Document Accessibility: PDFs, Word and Slides
On this page
Document accessibility is the practice of making every document you publish usable by people who rely on assistive technology, across all the formats you work in: PDFs, Word files, PowerPoint decks, spreadsheets and email. The formats differ, but the requirements do not: real structure, a logical reading order, text alternatives, a declared language and a title. What changes is where you do the work, and the most important lesson is that the fix is usually upstream in the authoring tool, not in the PDF.
Where do PDFs fit?
PDFs are where compliance deadlines land, because they are what organisations publish: reports, agendas, forms, policies and notices. The PDF accessibility guide covers them in depth. But a PDF is usually an export of something, and the quality of its tags depends entirely on the quality of the source. A Word file with real heading styles exports a clean tagged PDF. A Word file built from text boxes and bold text exports a tagged PDF that is still hard to read.
That is why the first question in any remediation workflow is whether you still have the source. If you do, fix the source and re-export; the step-by-step export guide covers both routes. If you do not, you remediate the PDF itself. Most archives are the second case.
Why the fix is usually upstream
Accessibility done upstream is cheaper, more accurate and easier to maintain. Three reasons:
- The tags come from real structure. A heading style produces an
H2tag; bold text produces nothing. Exporting a well-structured source gives you correct tags for free. - You fix it once. A corrected source re-exports a correct PDF every time it changes. A patched PDF has to be patched again after the next edit.
- It catches problems earlier. Alt text, table headers and reading order are set where the author is, not by a coordinator opening a tags panel weeks later.
The practical implication for a team is a rule, not a tool: apply heading styles, set a title, add alt text and mark table headers while you write, and the export takes care of itself. The accessible PDF checklist turns that into a per-file list for the export step.
What to do for each format
| Format | The fixes that matter |
|---|---|
| Word | Real heading styles, alt text on images, marked table header rows, a document title in properties, a set language |
| PowerPoint | Use the built-in layouts, a unique title on every slide, alt text on images, a logical slide order, read the slide in the outline view to check order |
| Excel / spreadsheets | Named sheets, a clear header row, no merged cells in data, table names, alt text on charts, a text summary for complex sheets |
| Google Docs and Slides | Real heading styles, alt text, a meaningful document name, and export with structure rather than as an image |
| A tag structure, reading order, alt text, language, title; export from source when you can, remediate when you cannot | |
| Real headings in the HTML, descriptive link text rather than “click here”, alt text on images, adequate contrast |
The table is short on purpose. The same five requirements, structure, order, alternatives, language, contrast, recur in every row. Learn them once and they transfer.
Where PDFs still need separate work
Even with good authoring practice, PDFs need their own handling in two situations. First, PDFs you receive from outside: vendor files, other departments’ exports, scans with no source. Second, PDFs that were authored badly before the practice existed, which is most archives. For both, the file itself has to be remediated, and that is the gap the free checkers do not close. The PDF accessibility checker guide covers the checking half, and how to remediate a PDF the fixing half.
A remediation aid such as TagRight is for that second group: it writes the tag structure, reading order, language and title into a PDF you did not author, leaves the pages looking the same, and returns a report of what still needs a human. It is a remediation aid, not a certification, and a binding document should be confirmed with PAC 2024 or veraPDF. For a public entity working to a deadline, the ADA compliant PDF guide covers the dates and obligations, and the Section 508 PDF guide covers the federal side.
A starting plan for a team
- Write the rule down. Apply heading styles, set a title, add alt text, mark table headers. Put it where authors will see it.
- Fix the authoring templates. A template with styles and a title field baked in does most of the work for you.
- Test before publishing. Run new documents through a free checker and read the important ones with a screen reader.
- Triage the archive. Sample by type and age, prioritise by risk, and remediate in batches.
- Keep a record. File, date, method and result, so you can show what you did.
Accessibility is a practice, not a purchase, and the practice is mostly upstream. For the standards behind it, WCAG 2.1 is the yardstick and Section508.gov covers the federal obligations. The PDF accessibility guide is the place to start for the format that carries the deadline. If you have a folder of PDFs with no source, the free tier for tagging them is on the pricing page, and you can tag a PDF free to see the report one produces.
Frequently asked questions
What is document accessibility?
It is the practice of making documents usable by people who rely on assistive technology, across every format you publish: PDFs, Word files, PowerPoint decks, spreadsheets and email. Each format has its own fixes, but the underlying requirements, structure, reading order, alt text, language and contrast, are shared.
Is document accessibility only about PDFs?
No, though PDFs are where most compliance deadlines land because they are what gets published. Word, PowerPoint and spreadsheet files are often the source, and fixing accessibility there is what makes the exported PDF accessible in the first place.
Why fix the source document instead of the PDF?
Because the tags in an exported PDF are generated from the source structure. A document with real heading styles, alt text and a title exports a clean tagged PDF. Fixing the PDF alone means redoing the work every time the source is updated.
What is the most common document accessibility failure?
Missing structure: headings faked with bold text, images with no alt text, and tables with no header rows. These are the same failures across formats, and they are quick to fix in the authoring tool.
Are email and spreadsheets covered by accessibility rules?
If they are published or used to deliver information to the public, they fall under the same obligations as other content. WCAG 2.1 AA is the yardstick for public-sector work, and it applies to the content rather than to a single file format.