Accessible statements, bills, and notices at scale: fixing the template instead of the document

A monthly statement is the document a customer with a disability most needs to read independently and the one least likely to have been designed for it. Statements, bills, explanations of benefits, and notices are produced by composition systems from a template plus data, in volumes that make per-document remediation impossible. That is also what makes them tractable: a template fixed once produces accessible documents forever. This guide sets out the legal expectations, the template-level fixes, and a validation model that works at volume.

What the law expects

United States, public entities. The ADA Title II web rule requires WCAG 2.1 AA for web content including documents, with an exception in 28 CFR 35.201(d) for conventional electronic documents that are about a specific individual, their property, or their account and are password-protected or otherwise secured; the DOJ's fact sheet gives a water or tax bill as the example. The exception covers the individual documents, not the portal that delivers them, and the fact sheet is explicit that the ADA's effective communication obligation still applies: a customer who asks for an accessible bill must get one. The HHS Section 504 rule for health providers contains provisions that mirror the Title II rule, so explanations of benefits and patient statements sit in the same position; see the HHS rule.

United States, private businesses. The ADA Title III regulations do not name a technical standard for documents the way the Title II rule does, and accessibility of statements has been pursued through complaints and litigation rather than a document rule. Providing statements that work with assistive technology, and an accessible format on request, is the defensible position.

European Union. The European Accessibility Act applies to consumer banking services and e-commerce services provided after June 28, 2025 (Article 2(2)). Annex I requires, for banking, that identification methods, electronic signatures, security, and payment services be perceivable, operable, understandable, and robust, and that information be understandable at no more than level B2 of the Common European Framework. The Act excludes office file formats published before June 28, 2025 from its website content requirements, which does not help with a statement generated next month. Microenterprises providing services are exempt. See EN 301 549 and the EAA.

Why generated statements fail

• Print streams converted to PDF. Many composition systems produce a print format (AFP, PCL, PostScript) and convert it, yielding a PDF with positioned text and no structure, or in the worst case a page image.
• Tables drawn as lines. Transaction tables are often drawn as text at coordinates with rules between them, so nothing marks a row, a column, or a header.
• Charts with no data. Spending breakdowns and usage graphs are images with no alternative and no table.
• Generic titles and no language. Every document is titled "Statement" or carries the file name, and the language is unset even where customers are served in several.
• Boilerplate as body text. Regulatory notices in tiny type are real content and must be readable, not treated as decoration.

Fix the template

1. Choose an output path that writes structure. If the composition engine can emit tagged PDF or PDF/UA, turn it on and map template elements to tags; if it renders HTML, the HTML to tagged PDF guide covers engines that write tags from semantic markup. If it can only emit print streams, that is the constraint to change.
2. Make the transaction table a real table. Header row as TH cells with Scope, one row per transaction, amounts and dates in consistent columns, and a caption or heading that names the period.
3. Give every chart a data table. A spending chart's data already exists in the record; render it as a tagged table after the figure and give the figure a short alt. See alt text for charts.
4. Set a unique title and the customer's language. "Statement for account ending 4821, June 2026" is a title; "Statement" is not. Set the document language from the customer's language preference; see the document settings guide.
5. Structure the page. Headings for each section (summary, transactions, fees, messages), lists for lists, running headers and footers as artifacts, and reading order that follows the visual order rather than the print stream's drawing order.
6. Handle security. If statements are encrypted, set the permission that allows assistive technology to extract text; a locked statement is unreadable no matter how it is tagged.
7. Offer an alternative format. An HTML statement in the portal, or large print, braille, or audio on request, is both a legal safety net and the format many customers prefer on a phone.

Validate by sample, per template version

Checking every generated document is neither possible nor necessary, because documents from the same template version share the same structure. Treat the template as the unit of assurance:

• Put a PDF/UA validator in the build pipeline and fail the build on a template change that introduces a machine-detectable error; the checker comparison covers veraPDF and PAC.
• For each template release, generate a sample that exercises every variant (multiple pages, zero transactions, foreign-currency lines, the longest message block) and run the screen reader procedure on it.
• Keep the sample, the validator output, and the screen reader notes with the template version as evidence, and repeat when the template, the engine, or the fonts change.
• Watch the boundaries: a new marketing insert, a regulatory notice added as an image, or a redesigned chart is a template change even if the engineering team does not call it one.

Frequently asked questions

Sources

The statements above rest on the primary sources below. Where a source is a law or standard, the version and date named in the text are the ones checked on the review date. This guide is general information, not legal advice.

1. eCFR: 28 CFR 35.201, Exceptions . The individualized, password-protected conventional electronic documents exception.
2. ADA.gov: Fact Sheet on the Title II web and mobile rule . The water or tax bill example and the statement of what the exceptions do not change.
3. Federal Register, May 11, 2026: Extension of Compliance Dates, Accessibility of Web Content and Mobile Applications of Recipients of Departmental Financial Assistance (HHS) . The Section 504 rule mirrors the Title II rule's provisions.
4. EUR-Lex: Directive (EU) 2019/882 (European Accessibility Act), Articles 2 and 4 and Annex I Section IV
5. veraPDF documentation: CLI validation