Skip to main content
PlugMonkey
Updated June 2026 · WCAG 2.2 + ISO 14289 (PDF/UA) aligned

PDF Accessibility Checklist for Chrome (2026): WCAG-Aligned Reader Setup

Roughly 16% of the global population lives with a significant disability (WHO, 2023), and PDFs remain one of the least accessible document formats on the web. This 10-step checklist walks you through the reader-side configuration that brings Chrome's PDF experience into line with WCAG 2.2 and ISO 14289 (PDF/UA) — the parts you control without needing to re-author the document.

Beginner
12 minutes
10 steps

By PlugMonkey Team, Editorial

TL;DR

This checklist is reader-side only — it covers the accessibility configuration you control when reading PDFs in Chrome, not the document-creation work that determines whether a PDF is fundamentally accessible. Enhanced PDF Viewer (free, built on Mozilla PDF.js) provides the reader-side surface: high-contrast themes for low-vision and photophobic readers, built-in text-to-speech via the W3C Web Speech API for hands-free or low-vision reading, complete keyboard-only navigation (page flip, jump, rotate, zoom) for motor-impaired users, semantic markup that screen readers like NVDA, JAWS, and VoiceOver can navigate, and a color-coding annotation palette that pairs with text labels for color-blind users. Two honest limitations the checklist flags explicitly: the extension cannot add PDF/UA tags to documents that don't have them — tagging is a document-creation concern, and untagged PDFs produce poor screen reader output regardless of which reader app you use; and image-only PDFs (scanned documents, screenshots saved as PDF) cannot be made TTS-accessible without an OCR pass to produce a text layer. The checklist sequence is: enable high-contrast theme, set comfortable text size and zoom, configure TTS voice and rate, verify keyboard-only navigation, check screen reader compatibility, use color-blind-safe annotation patterns, save annotated copies with the annotation layer preserved, inspect documents for tagged structure, configure accessibility-friendly print settings, and report systemically inaccessible PDFs to publishers.

  • WCAG 2.2 is the current W3C web accessibility standard (October 2023); PDF/UA is ISO 14289 — both inform the checklist below.
  • Enhanced PDF Viewer is reader-side accessibility: high-contrast themes, TTS, keyboard navigation, screen reader support, color-blind-safe annotation. It does NOT add PDF/UA tags to untagged documents.
  • Image-only PDFs (scanned documents, screenshots) need an OCR pass before TTS works — this is a document property, not a reader limitation.
  • Two reader-side actions everyone should do before reading any PDF: enable a high-contrast or dark theme, and verify the document is keyboard-navigable end-to-end.
“Web Content Accessibility Guidelines (WCAG) 2.2 covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content more accessible to a wider range of people with disabilities, including accommodations for blindness and low vision, deafness and hearing loss, limited movement, speech disabilities, photosensitivity, and combinations of these, and some accommodation for learning disabilities and cognitive limitations.”
— W3C — Web Content Accessibility Guidelines (WCAG) 2.2 — the current W3C Recommendation as of October 2023, applied here to the reader-side PDF surface. · w3.org/TR/WCAG22

The Numbers, By the Source

Every figure below cites a primary source. Click through to verify.

1.3 billion

Number of people globally — approximately 16% of the world's population — who experience a significant disability per the WHO 2023 Global Report on Health Equity for Persons with Disabilities. This includes low vision, blindness, hearing loss, motor impairment, cognitive disability, and combinations thereof. Each is a population whose PDF reading experience depends on reader-side accessibility configuration.

Source: World Health Organization — Disability Fact Sheet2024

WCAG 2.2 (Oct 2023)

The current W3C Recommendation for web accessibility, published October 5, 2023. WCAG 2.2 added nine new success criteria over WCAG 2.1, with focus visibility, dragging movements, and target size among the most relevant for PDF readers. This is the standard reader-side PDF accessibility is now measured against.

Source: W3C — Web Content Accessibility Guidelines 2.22023

ISO 14289-1

The international standard (commonly called PDF/UA — PDF/Universal Accessibility) that defines accessibility requirements for PDF documents, including tagged structure, alternate text for images, defined reading order, and language attributes. Document-creation standard, not a reader standard — but the structure it requires is what assistive tech consumes.

Source: ISO — Document management applications: PDF/UA2014

4.5:1

Minimum text-to-background contrast ratio required by WCAG 2.2 success criterion 1.4.3 (Contrast Minimum) for AA conformance. Enhanced PDF Viewer's high-contrast theme exceeds this ratio; the default Chrome PDF viewer with no dark mode often fails it for users reading at low ambient brightness.

Source: W3C — WCAG 2.2 Contrast (Minimum)2023

Before You Start

  • Google Chrome installed (current stable channel — accessibility APIs improve every release)
  • Enhanced PDF Viewer installed from the Chrome Web Store (free, no account)
  • Familiarity with your assistive technology — screen reader (NVDA, JAWS, VoiceOver, TalkBack), screen magnifier, keyboard-only navigation, or system TTS
  • Optional: a system voice installed for your preferred language if you'll use built-in text-to-speech
  • Optional: a high-contrast OS theme matched to your reader preference
1

Step 1 — Enable a High-Contrast Theme

The first reader-side accessibility configuration is theme. Chrome's built-in PDF viewer has no theme controls — PDFs render with a white background regardless of OS or Chrome dark mode (as documented in the Chrome PDF dark mode FAQ). After installing Enhanced PDF Viewer, open any PDF and click the theme icon in the toolbar. Pick from Light, Dark, High Contrast, or Match System. High Contrast applies the strongest text-to-background ratio (well above WCAG 2.2's 4.5:1 minimum for AA conformance) and is the appropriate choice for low-vision readers, users with photophobia or migraine triggers, and anyone reading in a low-light environment. The theme persists across documents and across browser sessions — you set it once.
Pro Tip

Match System is the right default for most users — it follows your OS accessibility setting, so changes to your system theme propagate to PDF reading automatically. Pick a specific theme (Dark, High Contrast) only when you want the PDF reader to override your system preference.

2

Step 2 — Set Comfortable Text Size and Use Smart Zoom

Text size matters as much as theme. Use Ctrl++ (Cmd++ on Mac) to zoom in until text is comfortable to read — there is no "correct" size, only the size that works for your vision and reading distance. Enhanced PDF Viewer's smart zoom cycle shortcut cycles through three sensible fit modes (fit-to-page, fit-to-width, actual size) with a single keystroke, so you can quickly switch between an overview and a reading-comfort zoom level. The viewer remembers per-document zoom, so a textbook chapter you annotated yesterday opens at the same zoom today. For users who routinely need 200-300% zoom, the WCAG 2.2 success criterion 1.4.4 (Resize Text) requires text to remain readable up to 200% — Enhanced PDF Viewer supports zoom up to 800% without UI breakage.
Pro Tip

Pair high zoom with a wider browser window. At 200%+ zoom, scrolling horizontally to read each line is fatiguing; widening the Chrome window so each line fits horizontally cuts scroll fatigue dramatically.

3

Step 3 — Configure Text-to-Speech (TTS)

Built-in TTS is the highest-impact accessibility feature in Enhanced PDF Viewer. It uses the W3C Web Speech API to read PDFs aloud using voices installed on your operating system. Click the speaker icon in the toolbar to open the TTS panel. Pick a voice (your system's installed voices in any language), adjust the speech rate (most users prefer 1.0 to 1.3x normal speed; advanced TTS users go up to 2.0x), and adjust pitch and volume to taste. Click Play. The viewer highlights the current sentence as it reads, which doubles as visual reinforcement for users with cognitive or learning disabilities. TTS works for hands-free reading (motor impairment), proofreading by ear (low vision, dyslexia, or just catching mistakes the eye skips), low-vision reading where text size alone isn't enough, and as a complement to screen readers when the PDF's tagged structure is imperfect.
Pro Tip

On macOS, install enhanced voices via System Settings → Accessibility → Spoken Content → System Voice → Manage Voices (look for voices marked 'Enhanced' or 'Premium'). On Windows, install voices via Settings → Time & Language → Speech → Add voices. These higher-quality voices make long-form TTS reading dramatically less fatiguing.

Important

TTS only works on PDFs with a text layer. Image-only PDFs (scanned documents, screenshots saved as PDF, photographs of paper documents) have no text for the speech engine to read. For these, you need an OCR pass first to produce a text layer — see Common Pitfalls below.

4

Step 4 — Verify Keyboard-Only Navigation Works End-to-End

Keyboard-only navigation is non-negotiable for users with motor impairments, RSI, or who prefer keyboard-driven workflows. Open a PDF, then disable your mouse (or just keep your hands off it) and walk through these actions: Page Up / Page Down to scroll, Ctrl+Page Up / Ctrl+Page Down for full-page flipping, Home / End to jump to start or end of the document, number keys for direct page jumping, Ctrl+F to search, Ctrl++ / Ctrl+- for zoom, and Ctrl+Shift+R for rotation. If every action works without the mouse, the document is keyboard-accessible at the reader level. Enhanced PDF Viewer's complete keyboard coverage is documented in the keyboard shortcuts FAQ.
Pro Tip

Use <kbd>Tab</kbd> to move keyboard focus between toolbar controls. WCAG 2.2 success criterion 2.4.11 (Focus Not Obscured) requires the focused control to remain visible — Enhanced PDF Viewer's focus indicators are designed to meet this; if you find any state where focus is hidden, that is a reportable bug.

5

Step 5 — Verify Screen Reader Compatibility

Screen reader compatibility depends on both the PDF reader (which must expose semantic markup) and the document (which must have tagged structure). Enhanced PDF Viewer exposes PDF.js's semantic markup — headings, lists, tables, and paragraph structure — to assistive technologies via standard ARIA roles. Test it with your screen reader: open a tagged PDF, then use your screen reader's navigation commands (NVDA: H for next heading, K for next link; JAWS: similar; VoiceOver: VO+Cmd+H for next heading). Navigation by heading, by list, and by paragraph should work. If it doesn't, the cause is almost always the document — an untagged or incorrectly tagged PDF — not the reader.
Important

Enhanced PDF Viewer does NOT add tags to untagged PDFs. Tagging is a document-creation responsibility — the document author or publisher must produce a tagged PDF in the first place. Reading an untagged PDF with a screen reader produces flat, unstructured output regardless of which PDF reader app you use. There is no reader app on any platform that retroactively tags untagged PDFs reliably; the structural information simply isn't in the file.

6

Step 6 — Use Color-Blind-Safe Annotation Patterns

If you annotate PDFs (for note-taking, collaboration, or review), the five-color palette in Enhanced PDF Viewer is useful — but per WCAG 2.1 success criterion 1.4.1 (Use of Color), color alone is insufficient as a meaning signal. For users with color-vision differences (approximately 8% of men and 0.5% of women — roughly 300 million people globally), red and green can be indistinguishable, and blue-yellow can be hard to differentiate for users with tritanopia. The fix is to pair color with a non-color signal: always add an inline comment to highlights where the color carries meaning, so the comment text disambiguates the highlight purpose. If you share annotated PDFs with others, write the color key into a sticky note on page 1 — the key is then visible regardless of the recipient's color perception.
Pro Tip

If you frequently collaborate with color-blind reviewers, switch your highlight convention to position-based: top of paragraph = fact, mid-paragraph = question, end of paragraph = todo. Position is universally readable and works alongside (or instead of) color.

7

Step 7 — Save Annotated Copies With the Annotation Layer Preserved

When you annotate a PDF for a screen-reader-using collaborator, the annotated download must preserve the annotation text so the collaborator can read your comments via screen reader. Enhanced PDF Viewer bakes annotations into the downloaded PDF as standard ISO 32000-2 annotation objects, which means the comment text is exposed to screen readers via the document's accessibility tree (assuming the underlying document is tagged). Verify by opening the downloaded annotated copy in a separate PDF reader and using your screen reader's annotation-navigation command — NVDA exposes annotations via Ctrl+Alt+A; VoiceOver via the rotor. If the annotations are reachable, your annotated PDF is screen-reader-friendly.
Pro Tip

Write annotation comment text as if it will be read aloud — short, complete sentences without UI-only references like 'see the yellow above.' The comment will be read in isolation by the screen reader, with no visual context.

8

Step 8 — Inspect Documents for Tagged PDF Structure

Before committing to a long reading session with a screen reader, quickly check whether the document is tagged. With Enhanced PDF Viewer, open the document outline panel (the table-of-contents icon in the sidebar). If the outline shows a populated tree of headings, the document is tagged for structure and your screen reader will be able to navigate by heading. If the outline is empty or shows only a single flat list, the document either has no tags or has minimal structure — your screen reader will read the document as flat text. This is your decision point: a tagged PDF is worth reading via screen reader; an untagged PDF is worth converting to HTML or DOCX first, where tag-rebuilding tools (Microsoft Word's accessibility checker, Adobe Acrobat's tagging) work better than they do on PDF.
Pro Tip

If you regularly receive untagged PDFs from a specific publisher (a government agency, a journal, a vendor), report it to them with reference to ISO 14289 (PDF/UA). Many publishers will fix accessibility once a specific complaint references the standard.

9

Step 9 — Configure Accessibility-Friendly Print Settings

Sometimes the most accessible workflow is reading a printed copy with a magnifier, large-print readers, or alongside a tactile workflow. Enhanced PDF Viewer's professional print dialog (Ctrl+P) exposes accessibility-friendly options that Chrome's built-in print dialog doesn't: page range selection (print only the pages you need, not the whole 300-page document), DPI selection (300 DPI for sharper text), and grayscale toggle (which can improve contrast for some low-vision readers). Pair these with your printer's own large-print or contrast settings. For users with low vision who prefer print, the combination of Enhanced PDF Viewer's high-contrast theme rendering, 300 DPI print, and a printer set to maximum darkness produces the most readable hard copy you can get from a standard laser printer.
10

Step 10 — Report Inaccessible PDFs to Publishers

The reader-side configuration above only goes so far — if the underlying document is fundamentally inaccessible (untagged, image-only without OCR, missing alt text on images, broken reading order), the right fix is for the document author or publisher to produce an accessible version. When you encounter a systematically inaccessible PDF from a publisher, agency, or vendor, report it. A useful template: "The PDF at [URL] does not conform to ISO 14289-1 (PDF/UA) or WCAG 2.2 — specifically, [the document is untagged / lacks a text layer / has no alt text on images / has incorrect reading order]. This makes the document unusable for [low vision / motor impairment / dyslexia / screen reader] users. Please provide an accessible version per Section 508 / EN 301 549 / your jurisdiction's equivalent." Many publishers will fix accessibility on request when the request references a specific standard.
Pro Tip

U.S. federal agencies are required to provide accessible PDFs per <a href='https://www.section508.gov/' target='_blank' rel='noopener'>Section 508 of the Rehabilitation Act</a>. EU public-sector bodies are required to per the EU Web Accessibility Directive (EN 301 549). Reference the legal requirement in your report — it's often the strongest argument for prioritizing the fix.

Summary

Reader-side PDF accessibility in Chrome is a configuration problem that has a known solution: install Enhanced PDF Viewer to gain a high-contrast theme system, built-in TTS via the W3C Web Speech API, complete keyboard navigation, semantic markup exposed to screen readers, and a color-blind-safe annotation workflow paired with text labels. The 10-step checklist above covers everything you control as a reader — what you cannot control is the document itself. Untagged PDFs and image-only PDFs are inaccessible at the document level, and no reader application on any platform can retroactively fix the missing structural information. The right response is twofold: use OCR tools to add a text layer to image-only PDFs you must read, and report systematically inaccessible PDFs to publishers with reference to ISO 14289 (PDF/UA), WCAG 2.2, and your jurisdiction's accessibility law (Section 508 in the U.S., EN 301 549 in the EU, AODA in Ontario). PDF accessibility has been a known concern for decades and PDF/UA has existed as ISO 14289 since 2014 — most accessibility failures in 2026 are publisher-side neglect, not technical impossibility. The reader-side checklist makes accessible documents readable in Chrome; the publisher-side accountability is what fixes the long tail of inaccessible documents.

Need More Help?

Get personalized AI assistance with additional tips and troubleshooting.

Ask ChatGPT(opens in new tab)Ask Perplexity(opens in new tab)Ask Claude(opens in new tab)

AI responses are generated independently and may vary

Related Guides

How to Annotate PDFs in Chrome: A Step-by-Step Workflow GuideHow to Highlight and Annotate Web ArticlesHow to Save and Organize Articles with ReadMonkey Pro

Frequently Asked Questions

Sources & Further Reading

  1. Web Content Accessibility Guidelines (WCAG) 2.2 — W3C Recommendation, October 2023. The current standard for web accessibility, including reader-side PDF surfaces. — W3C — World Wide Web Consortium (accessed Jun 1, 2026)
  2. WCAG 2.2 — Understanding Success Criterion 1.4.3 (Contrast Minimum). Defines the 4.5:1 contrast ratio for AA conformance. — W3C Web Accessibility Initiative (accessed Jun 1, 2026)
  3. ISO 14289-1:2014 — Document management applications — Electronic document file format enhancement for accessibility (PDF/UA-1). The international standard for PDF accessibility. — International Organization for Standardization (accessed Jun 1, 2026)
  4. WHO — Disability and Health Fact Sheet. Cites 1.3 billion people (16% of global population) living with significant disability. — World Health Organization (accessed Jun 1, 2026)
  5. Web Speech API — MDN reference. The W3C-spec API Enhanced PDF Viewer uses for text-to-speech. — MDN Web Docs / Mozilla (accessed Jun 1, 2026)
  6. Mozilla PDF.js GitHub repository — semantic markup and accessibility tree exposure for screen reader compatibility. Apache 2.0 license. — Mozilla Foundation / GitHub (accessed Jun 1, 2026)
  7. Section 508 of the Rehabilitation Act — U.S. federal accessibility requirements for electronic documents including PDFs. — U.S. General Services Administration (accessed Jun 1, 2026)

More Resources

FAQCommon QuestionsIntegrationsWorkflow ConnectionsGlossaryKey Terms Explained

Make Every PDF in Chrome More Accessible — Free Forever

Enhanced PDF Viewer adds high-contrast themes, built-in text-to-speech, full keyboard navigation, and screen reader compatibility to Chrome's PDF viewer — built on Mozilla PDF.js, 100% local, no account, no telemetry. Install once and every PDF you open gets the reader-side accessibility surface this checklist describes.

Install Free — Chrome Web Store(opens in new tab)Learn More