Accessibility is now a market-entry requirement for multilingual manuals. Since automated checks catch only 30–40% of defects, this guide sets out the accessibility items to check against EAA, ADA, WCAG, PDF/UA, and EN 18339.
- Who it’s for Technical writers, documentation managers, localization and QA reviewers, and manufacturers producing manuals with AI tools.
- When to use Right after building your digital or print deliverables, just before accessibility sign-off, and when preparing to launch in the US or EU.
- See also Run the companion “Multilingual Manual Accessibility Checklist (19 items)” for a quick self-assessment.
In the US, document accessibility is enforced through the Americans with Disabilities Act (ADA) and Section 508 of the Rehabilitation Act, and WCAG 2.1/2.2 Level AA has become the working standard. If you also ship to the EU, the European Accessibility Act (EAA) has required accessible instructions and online documentation for products placed on the EU market since June 28, 2025. Accessibility is no longer “nice to have” — it is a condition of market entry.
Automated accessibility checkers catch only about 30–40% of issues. The rest require hands-on testing with assistive technology (screen readers and the like) and informed manual review.
1. Why accessibility is now a regulatory requirement
Digital PDFs must meet PDF/UA (ISO 14289); printed manuals and on-package labeling shipped to the EU must meet EN 18339. WCAG 2.1/2.2 Level AA is already the global baseline. Multilingual delivery adds further variables:
- Per-language lang attributes — so screen readers identify each language automatically
- Correct screen-reader reading order for RTL (right-to-left) languages
- Text-to-speech (TTS) quality for non-Latin scripts (Chinese, Japanese, Korean, and others)
2. Five accessibility areas to verify in multilingual work
Even a linguistically perfect translation does not make a document usable. Designing the semantic structure so that users with visual, hearing, cognitive, or motor disabilities can navigate it with assistive technology is a separate technical discipline.
| Area | What to verify |
|---|---|
| Regulatory scope | ADA, Section 508, and EAA applicability analysis; declaring WCAG, PDF/UA, EN 18339 |
| Digital accessibility | Color contrast, alt text, semantic structure, keyboard access, focus indicators, PDF/UA |
| Multilingual accessibility | Language attributes, RTL reading order, CJK text-to-speech |
| Non-digital accessibility | EN 18339, minimum type size, alternative channels, multisensory paths |
| User testing & sign-off | Hands-on assistive-technology testing, conformance statement, audit-ready records |
3. The 19 checks in five categories
Hansem’s standardized accessibility checks span five categories and 19 items in total. Each is graded Critical (A), Major (B), or Minor (C). Critical (A) items must be at zero before sign-off — a single miss can be an ADA/Section 508 or EAA violation that blocks market entry or public procurement.
| Category | Scope | Items |
|---|---|---|
| A. Regulatory scope | EAA, ADA / Section 508, declaring standards | 3 |
| B. Digital accessibility | Contrast, alt text, semantic structure, keyboard, focus, PDF/UA | 6 |
| C. Multilingual accessibility | Language attributes, RTL, non-Latin TTS | 3 |
| D. Non-digital accessibility | Printed manuals/labels, type size, alternative channels, multisensory | 4 |
| E. User testing & sign-off | Assistive-technology testing, conformance statement, evidence retention | 3 |
4. The five issues most often caught right before delivery
None of these are caught by automated or visual review alone.
- PDF not generated as a tagged PDF
→ Fails Section 508 / ADA and the EAA; ineligible for government procurement - Language attribute hard-coded to English across all languages
→ Screen readers fail to switch languages; WCAG violation - Safety information distinguished by color alone
→ WCAG 1.4.1 violation; color-blind users cannot perceive safety information - Body text printed at 6–7 pt
→ Fails EN 18339 minimum type size; breaches EAA non-digital requirements - No accessibility conformance statement
→ No VPAT/ACR for US procurement; subject to post-market enforcement in the EU
Wrong vs. right — three representative cases
| WRONG ✗ | RIGHT ✓ | |
|---|---|---|
| PDF/UA | The PDF manual is not a tagged PDF, so screen readers cannot access it. | Tagged PDF with correct reading order and alt text. |
| Color contrast | Body-text-to-background contrast is 3:1 — a WCAG 1.4.3 violation. | 4.5:1 or higher (3:1 for large text). |
| Language attribute | Every language page is hard-coded to html lang=”en” — language detection fails. | Per-language lang attributes applied (including inline language switches). |
6. Run it as a two-stage cross-check
Multilingual accessibility carries far more variables (lang control, RTL migration, and the like) than single-language review, so it cannot rest on automated checks alone. Splitting the work into two stages reduces legal risk:
- Author self-check — a first pass with the checklist right after the build.
- Reviewer cross-check — before final release, a separate person runs hands-on assistive-technology testing.
Frequently asked questions
- Are PDF manuals covered by accessibility requirements?
Yes. Digital PDFs must meet PDF/UA (ISO 14289): a tagged PDF with correct reading order, alt text, and heading structure. - Do the ADA and Section 508 apply to our product documentation?
If you sell to US federal or state government, or operate places of public accommodation, your digital documents fall under Section 508 and the ADA. WCAG 2.1/2.2 Level AA is the working benchmark. - When does the EAA apply?
Since June 28, 2025, it applies to the instructions and online documentation of products placed on the EU market. - Is an automated checker enough?
No. Automated tools catch only about 30–40% of issues. The rest requires hands-on assistive-technology testing and expert review. - Do printed manuals have accessibility requirements?
Yes, for EU shipments under EN 18339: minimum type size, multisensory paths, and an alternative digital channel (for example, a QR code). - What extra requirements apply to multilingual manuals?
Language (lang) attributes, correct RTL reading order, and TTS quality for non-Latin scripts (CJK and others).
Multilingual Manual Pre-Launch QA Series (8 parts)
This series walks through the eight pre-launch checks a multilingual manual must pass, from translation intake to final release. Each part comes with a guide and a self-check checklist.
- 1 Translation Integrity — Pre-edit defect screening of translated content
- 2 DTP — Multilingual typesetting and layout integrity
- 3 Regulatory — Market-specific regulatory and standards markings
- 4 UI Matching — Aligning the product UI with the manual
- 5 Accessibility — ADA, Section 508, WCAG, PDF/UA checks (this article)
- 6 Multi-Channel Publishing — Cross-media consistency across PDF, HTML, and mobile from one source
- 7 Print Production — Print-ready PDF: bleed, CMYK, font embedding
- 8 Data Management — Archiving source files and translation memory for reuse
Hansem Global
Founded in 1990, Hansem Global specializes in multilingual technical documentation and localization for global manufacturers, operating a quality assurance system that spans the entire manual production process — from authoring and translation to digital and print publishing. www.hansem.com
This guide does not replace the source standards or applicable law, nor does it provide legal advice. Confirm the current version of each standard and market-specific requirements before final release.