Document accessibility testing checks whether PDFs, Word files, spreadsheets and slide decks can be read and completed by people using screen readers, keyboards and magnification. A reliable test has three layers: an automated checker such as the free PAC 2026 or Adobe Acrobat’s Accessibility Checker, a manual review of tags, reading order, alt text, tables and form fields, and a real screen reader pass with NVDA. Documents are judged against WCAG (Section 508 uses WCAG 2.0 AA, the ADA Title II rule uses WCAG 2.1 AA) and, for PDFs, the PDF/UA standard (ISO 14289).
This guide is written by HalfAccessible’s IAAP-certified testers, who audit and remediate documents for companies, universities and public bodies. It is practical guidance, not legal advice.
What Is Document Accessibility Testing?
Document accessibility testing evaluates digital files such as PDFs, Word documents, Excel spreadsheets and PowerPoint presentations to make sure people with disabilities can read, navigate and complete them.
Many organizations focus heavily on website accessibility while overlooking documents that contain critical information: application forms, policies, annual reports, menus, invoices and course materials. Accessible documents help ensure equal access to content while supporting regulatory compliance.
Why Accessible Documents Matter
Accessible documents improve usability for people who rely on screen readers, keyboard navigation, magnification software, reflow and other assistive technologies.
Supports Legal and Regulatory Compliance
Documents are covered by most accessibility laws, not just websites:
- Section 508 (US federal agencies and their suppliers): the Revised 508 Standards require electronic content, including PDFs, Word files, spreadsheets and presentations, to conform to WCAG 2.0 Level A and AA (E205.4). Non-web documents are exempt from only four criteria: 2.4.1 Bypass Blocks, 2.4.5 Multiple Ways, 3.2.3 Consistent Navigation and 3.2.4 Consistent Identification. Section508.gov publishes guides to creating accessible documents and accessible PDFs.
- ADA Title II (US state and local government, public schools and universities): the DOJ rule treats documents as web content and sets WCAG 2.1 Level AA. After the April 2026 interim final rule, the compliance date is April 26, 2027 for entities with a population of 50,000 or more and April 26, 2028 for smaller entities and special district governments (ADA.gov fact sheet). Older PDFs, Word, presentation and spreadsheet files posted before the compliance date are usually exempt, but not if people still use them to apply for, access or take part in a service, such as an application form.
- ADA Title III (US businesses): there is no DOJ technical standard for private websites, but documents customers need, such as menus, forms, policies and statements, can be cited in demand letters and lawsuits, and settlements commonly reference WCAG 2.1 or 2.2 AA.
- EU and UK: EN 301 549 has a dedicated clause 10 for non-web documents. The Web Accessibility Directive covers public sector office files published from 23 September 2018, and older ones still needed for active administrative processes. The European Accessibility Act can bring documents that are part of covered services, such as e-commerce and banking, into scope.
Public bodies preparing for the Title II dates can use our government accessibility audit request to scope websites and document libraries together.
Expands Access to Information
Accessible documents let every user find, understand and act on content independently, without asking for an alternative format.
Improves User Experience
Well-structured documents are easier for everyone to navigate, search and reuse, and they convert to other formats more reliably.
Which Standards Apply to Documents?
- WCAG 2.x: WCAG 2.2 is written for web content, but documents published on a website are web content too. For documents that are not on the web, the W3C’s WCAG2ICT note explains how to interpret each criterion, and the W3C publishes PDF techniques for meeting WCAG in PDF files.
- PDF/UA (ISO 14289): the international standard for universally accessible PDF. It defines how a PDF must be tagged and structured so assistive technology can use it. PDF/UA-1 (ISO 14289-1) applies to PDF 1.7 files and is the version the Section 508 standards and most checkers still reference. PDF/UA-2 (ISO 14289-2:2024), published in March 2024, applies the same idea to PDF 2.0 and adds features such as MathML support; it does not replace PDF/UA-1.
- The Matterhorn Protocol: the PDF Association’s testing model for PDF/UA-1. Version 1.1 lists 136 failure conditions grouped into 31 checkpoints: 87 can be determined by software alone, 47 usually need human judgement (for example, whether text that looks like a heading is tagged as one, or whether alt text is accurate) and 2 have no specific test. That split is why an automated pass is never the whole test.
Testing PDFs vs Word, Excel and PowerPoint
Office files and PDFs need different testing paths:
- Word, Excel and PowerPoint: use the built-in Accessibility Checker (Review, then Check Accessibility), then check headings in the Navigation Pane, alt text on images, table header rows, sheet names in Excel, slide titles and reading order in PowerPoint, and meaningful link text. Fixing the source file is usually far quicker than fixing the PDF exported from it.
- PDFs: check that the file is tagged, then test the tag tree, reading order, alt text, tables, forms, bookmarks and metadata with a PDF checker, then confirm with a screen reader and the keyboard.
How to Do Document Accessibility Testing: Step by Step
- Start with the source. If the PDF came from Word, PowerPoint or InDesign, check and fix the source first and re-export with tags.
- Run an automated checker. The free PDF Accessibility Checker (PAC) tests against PDF/UA and WCAG; Adobe Acrobat Pro has a built-in Accessibility Checker as well. WebAIM’s guide to PDF accessibility in Acrobat covers the Acrobat workflow.
- Inspect the tags and reading order. In Acrobat, open the Tags and Reading Order panels. Check that headings use H1 to H6 tags in a logical order, lists use list tags, tables have header cells, and decorative content is marked as an artifact.
- Check alternative text and links. Every informative image needs alt text, and link text should make sense on its own.
- Test forms. Fields must have labels (tooltips in PDF), a logical tab order and clear instructions.
- Check document properties. A meaningful title set to display in the title bar, the document language, and bookmarks for long documents.
- Test with a screen reader and keyboard. Read the document with NVDA or JAWS and Acrobat Reader, move by headings, Tab through links and fields, and confirm reading order. Our screen reader testing guide covers the basics.
- Check colour and contrast for text and important graphics.
The University of Washington’s guide to checking PDFs for accessibility is a clear, step-by-step companion to this process.
Document Accessibility Testing Tools (Including Free Section 508 Options)
No single tool proves a document is accessible, but the right combination finds most problems quickly. These are the tools our testers use:
| Tool | What it tests | Cost |
|---|---|---|
| PAC 2026 (PDF Accessibility Checker) | PDF/UA (ISO 14289) and WCAG 2.2 AA machine checks, plus a screen reader preview and logical structure view | Free (Windows) |
| Adobe Acrobat Pro Accessibility Checker | Full Check report, plus the Tags, Reading Order and Order panels for manual repair | Paid subscription |
| veraPDF | Open-source PDF/UA-1 and PDF/UA-2 validation, with a command line and Java library for checking documents automatically in a publishing pipeline | Free, open source |
| Microsoft Accessibility Checker | Built into Word, Excel and PowerPoint (Review, then Check Accessibility): missing alt text, headings, table headers, slide titles and more | Included with Microsoft 365 |
| NVDA screen reader | How the document is actually announced: headings, reading order, tables, form fields and links | Free (Windows) |
| Section508.gov authoring and testing guides | Step-by-step Section 508 test processes for Word and PDF | Free |
If you are looking for “508 testing software”, note that every tool above checks only part of WCAG. Section 508 conformance for a document still needs a person to judge alt text, reading order and meaning.
WCAG Success Criteria Most Relevant to Documents
| Criterion | What it means in a document |
|---|---|
| 1.1.1 Non-text Content | Images, charts and figures have alt text; decorative images are artifacts. |
| 1.3.1 Info and Relationships | Headings, lists, tables and form labels are tagged, not just styled. |
| 1.3.2 Meaningful Sequence | The reading order matches the logical order, including multi-column layouts. |
| 1.4.3 Contrast (Minimum) | Text meets 4.5:1 contrast (3:1 for large text). |
| 2.4.2 Page Titled | The document has a descriptive title shown in the title bar. |
| 2.4.6 Headings and Labels | Headings and labels describe topic or purpose. |
| 3.1.1 Language of Page | The document language is set. |
| 3.3.2 Labels or Instructions | Form fields have labels and instructions. |
| 4.1.2 Name, Role, Value | Form fields and buttons expose a name, role and value to assistive technology. |
Does WCAG 2.2 change PDF testing? Not much. PAC’s own introduction to PAC 2026 notes that its technical tests are based on WCAG 2.1, because the improvements in WCAG 2.2 are relevant to websites and PDF viewer programs rather than to PDF document content. PAC also runs additional quality checks, which are recommended best practices rather than an official standard.
Common Accessibility Issues Found in Documents
Untagged or Scanned PDFs
A PDF with no tags, or a scanned image of a page, gives a screen reader nothing to read. Scanned documents need OCR, and the recognised text must be checked for errors.
Missing Heading Structure
Documents without proper headings are hard for screen reader users to navigate; large bold text is not a heading unless it is tagged as one.
Images Without Alternative Text
Visual content must include meaningful descriptions when it is needed to understand the document. Our alt text guide explains how to write them.
Incorrect Reading Order
Screen readers may present content in a confusing sequence if the document structure is not properly defined, particularly in multi-column layouts, sidebars and text boxes.
Inaccessible Tables
Complex tables often lack header cells and relationships, making them difficult to interpret.
Decorative Content Not Marked as Artifacts
Page numbers, running headers, lines and background shapes get read aloud on every page.
Unlabelled Form Fields and Unclear Links
Fields with no tooltip are announced as “edit text”, and links such as “click here” give no context.
Missing Bookmarks, Title or Language
Long documents without bookmarks are hard to move around, and a missing language setting makes screen readers mispronounce the text.
Automated Checks vs Manual Document Testing
Checkers like PAC and Acrobat are essential for finding missing tags, alt text, title and language settings quickly. They cannot judge whether alt text is accurate, whether the reading order makes sense, or whether a heading is tagged at the right level. Like automated website testing, they are the first step; human review with assistive technology confirms the result.
Document Accessibility Testing Checklist
- Source file checked and fixed before export.
- PDF is tagged and passes PAC or the Acrobat checker.
- Headings, lists and tables are tagged correctly.
- Reading order is logical.
- Informative images have accurate alt text; decorative items are artifacts.
- Form fields have labels and a logical tab order.
- Title, language and bookmarks are set.
- Text contrast meets WCAG.
- Scanned pages have accurate OCR text.
- Screen reader and keyboard test passed.
For a full guide to creating accessible PDFs yourself, read our PDF accessibility guide. Document accessibility testing helps organizations ensure that critical information remains accessible, compliant and inclusive for all users.
How a Professional Document Accessibility Audit Works
If you publish more than a handful of documents, testing every file yourself is slow, and fixing them one by one is slower. In a HalfAccessible document accessibility audit, IAAP-certified specialists (CPACC, WAS and CPWA, plus a DHS Section 508 Trusted Tester) work like this:
- Inventory and sample. We group your PDFs, Word, Excel and PowerPoint files by template and purpose, and prioritise forms, applications, policies and anything people need to use a service.
- Test. Each sampled document goes through PAC or veraPDF, a manual tag, reading order, table and form review, and an NVDA screen reader and keyboard pass, mapped to WCAG and PDF/UA.
- Report. Every issue comes with its location, the WCAG criterion or Matterhorn failure condition, its severity and how to fix it in the source file or the PDF. See a sample audit report.
- Fix and re-test. Our PDF and document remediation team repairs the files or your templates, then we re-test them.
Document work is quoted per document set, because 10 simple letters and 10 long, form-heavy reports are very different jobs. Our guide to accessibility audit cost explains what moves the price. Websites are audited at fixed prices through our accessibility audit services: a $500 Quick Audit for up to 5 templates or a $2,000 Complete Audit for up to 25 templates or key user flows, both on our pricing page. US federal suppliers can pair documents with an ADA and Section 508 accessibility audit.
Work With Us
Not sure whether your PDFs, Word documents or reports would pass? Tell us what you publish and we will reply within 2 business days with a recommended scope.
Get a free accessibility needs assessment (four short questions, no commitment), or book a $100 consultation to review a sample of your documents live with a certified specialist.
