Accessible PDF Invoices, Receipts, and Order Documents for Online Stores

Checkout gets the audit and the invoice gets forgotten. Tagged PDF, reading order, and text based totals are what make an order document readable, and a HTML receipt often beats a PDF entirely.

After an accessible checkout, many stores email a PDF invoice that is a picture of a document. No text layer, no tags, no reading order. A screen reader opens it and finds nothing, or finds the totals before the items, or reads a table as a single run of numbers with no headers. For business customers that invoice is not a courtesy copy. It is the record their accounts team needs, and for a customer who cannot read it, the purchase is not finished.

PDF accessibility is a separate craft from web accessibility, with its own failure modes. The core requirements are the same ideas: real text, structure that a machine can follow, headings and table headers marked as such, and a reading order that matches the visual order. Documents generated from templates fail in the template, which means one fix repairs every invoice you send from then on.

What tagged PDF actually means

Tags are the PDF equivalent of HTML structure. They mark headings, paragraphs, lists, and tables, and they define the order in which content is read. An untagged PDF may still contain selectable text, which fools a quick check: you can highlight the words, so it looks accessible, but assistive technology gets them in the order they were drawn, which for a two column invoice layout can interleave the billing address with the line items.

Check a generated invoice in a checker and by reading it with a screen reader or a read aloud tool in reading order. Look specifically at the items table. Quantities, descriptions, unit prices, and line totals need header associations, or a listener hears a column of figures with nothing to attach them to. Totals, tax, and the amount paid should be plain text, never a scanned signature style image of a number.

The template is the fix

Invoices usually come from an accounting platform, an order management tool, or a plugin. Each has different PDF output, and some produce tagged output if a setting is switched on or a newer template is chosen. Ask the vendor directly whether their PDFs are tagged and conform to PDF/UA, and test the answer with a real file. Vendor claims in this area are optimistic, and the file does not lie.

Where the platform cannot produce an accessible PDF, provide the same information as accessible HTML. An order confirmation page and an email with the items, totals, and tax in real text covers the customer's need, and for many stores it is the pragmatic route: HTML receipts are easier to make accessible than retrofitted PDFs, and they are easier to search, forward, and archive.

Documents beyond the invoice

Gift receipts, return labels and instructions, warranty documents, and delivery notes all leave the store as PDFs or print. Returns instructions deserve particular attention, because a customer who cannot read them cannot complete a return within your window, and that is both an accessibility barrier and a consumer problem. Keep a text version of return steps on the site, linked from the order email, rather than only inside a parcel insert.

Set a rule for any new document template: no template ships until a sample output has been checked for tags, reading order, and text selectability, and the file name and document title are meaningful. Invoice final.pdf tells nobody anything. A document title set in the PDF properties is what a screen reader announces first, so use the store name, document type, and order number.

Related reading: Accessible Gift Wrapping, Gift Messages, and Receipt Options, Accessible Pre-Order Deposits and Balance Payment Pages, Accessible Preorder and Deposit Flows: Dates, Balances, and Honest Timers.

Frequently asked questions

How can I tell if a PDF invoice is accessible?

Open it and try to select and copy text, then run it through a PDF accessibility checker, then read it in reading order with a screen reader or read aloud feature. Selectable text alone is not enough. You are looking for tags, sensible reading order, and table headers on the items table.

What is PDF/UA?

PDF/UA is the ISO standard for accessible PDF, formally ISO 14289. It defines requirements such as tagging, reading order, and text alternatives so that a PDF can be used with assistive technology. Asking a document vendor whether output conforms to PDF/UA is a precise question with a testable answer.

Can I replace PDF invoices with HTML receipts?

For accessibility, HTML is often the better format, provided it contains the full record a customer needs: items, prices, tax, totals, addresses, and order identifiers. Some business customers and jurisdictions need a PDF or specific invoice fields, so check accounting and legal requirements before removing PDFs entirely.

Do order emails themselves need to be accessible?

Yes. Use real text rather than an image of the order, a logical heading structure, descriptive link text for tracking and returns, and tables marked up so items and prices associate correctly. An email that is one large image is the same barrier as an untagged PDF.