How to Make a Word Document Accessible: The Complete 2025 Checklist
A government-ready 2025 checklist for accessible Word (.docx) documents — headings, alt text, lists, tables, language, links, colour, and exporting.
Upload a .docx, run checks, auto-fix common issues, and download a cleaned file plus an audit report — all without your document ever leaving your device.
Built for government, business, higher-ed, and community groups. No signup. No servers.
Drag & drop your file here, or
No file handy? Try a sample:
Example 1 — Marketing Brief (Before) Example 1 — Marketing Brief (After) Example 2 — Policy Extract (Before) Example 2 — Policy Extract (After)“Before” docs include fake headings, raw URLs, tiny text, and tables without headers. “After” versions show the accessible structure.
Select a .docx or drag it in. Your document is processed locally and never leaves your device.
We flag common issues: fake headings & skipped levels, tiny text, missing image alt text, fake bullets, missing table headers, raw URLs, & missing language. Safe auto-fixes are applied if enabled.
Grab a cleaned .docx and a Markdown report for your records or internal QA workflows.
Heading 2.en-AU).Note: Full WCAG conformance depends on your final web format; this prepares Word docs for cleaner export (Word HTML / Mammoth / Pandoc).
See how Accessr improves document accessibility from “Before” to “After”.
Header for better export.Marketing Brief — Before Marketing Brief — After Policy Extract — Before Policy Extract — After
A government-ready 2025 checklist for accessible Word (.docx) documents — headings, alt text, lists, tables, language, links, colour, and exporting.
When to use accessible .docx vs tagged PDF, the export settings that matter, and how to avoid common pitfalls.
Why web-only publishing isn’t always inclusive — and how accessible Word or tagged PDF downloads preserve record integrity, accessibility, and transparency.
No. Everything runs in your browser using Web APIs. Your file never leaves your device.
Color contrast and complex shapes/SmartArt are limited in Word’s XML. This tool flags likely problems but can’t guarantee full WCAG compliance without exporting to HTML and running a web a11y scanner.
Yes—because processing is local. Always follow your organisation’s policies.
This MVP applies safe list styling. Advanced numbering (editing word/numbering.xml) can be added if you want a more opinionated fix pass.
We do not collect, transmit, or store your documents. All processing happens locally in your browser. If you host this page yourself, review any third-party analytics you add to ensure they do not capture document contents.