In Depth, On Demand Accessible Documents Training Starting Soon!
- November 2, 2026 - February 1, 2027
- December 7, 2026 - March 5, 2027
Registration is officially open for the above WebAIM Accessible Document Training cohorts (and yes, you can register after the start date), sponsored by the California Community Colleges (CCC) Accessibility Center. Register: WebAIM Accessible Document Training
Why Start Here
Word is where most documents begin — syllabi, handouts, reports, memos, and forms. Making a Word document accessible from the start takes only a few extra minutes. An accessible Word document also converts cleanly to an accessible PDF — one of the best reasons to start in Word.
⚡ Quick Reference
- Styles, not formatting: use heading styles, not bold/size
- Alt text on every image, or mark as decorative
- Built-in tools: lists, tables, columns
- Save As PDF — never Print to PDF
- Run the checker: Review → Check Accessibility
Step-by-Step: Making a Word Document Accessible
- Step 1: Set the Document Language
The language setting sets pronunciation rules for screen readers.
Review → Language → Set Proofing Language → English (or the appropriate language)- Step 2: Use Heading Styles
Don't use bold, large font, or color to create the appearance of headings — use the actual heading styles.
- Home → Styles → Heading 1 (for the document title — one per document)
- Home → Styles → Heading 2 (for major sections)
- Home → Styles → Heading 3 (for sub-sections)
- Don't skip levels (don't go from H1 to H3)
See Structure & Headings for why this matters.
- Step 3: Add Alt Text to Images
For every meaningful image:
- Right-click the image → Edit Alt Text
- Write a concise description of the image's meaning
- If the image is decorative, check "Mark as decorative"
- See Images & Alternative Text for guidelines on writing good alt text.
- Step 4: Use Real Lists
Use the built-in list tools — don't type bullets or numbers manually.
- Home → Bullets (for unordered lists)
- Home → Numbering (for ordered lists)
- Step 5: Create Accessible Tables
Only use tables for data, never for layout (design).
- Insert → Table (don't draw with tabs)
- Select the table → Table Design tab → check Header Row
- For long tables, select the header row → right-click → Table Properties → Row → check "Repeat as header row at the top of each page"
- Don't merge or split cells
See Tables for more detail.
- Step 6: Check Color Contrast
Ensure text and background colors meet the 4.5:1 minimum contrast ratio. If you're using colored text or a colored background, test it with the WebAIM Contrast Checker. See Color & Contrast for requirements.
- Step 7: Write Descriptive Link Text
Don't paste raw URLs. Instead:
- Select the text you want to use as the link
- Insert → Link (or Ctrl+K / Cmd+K)
- Enter the URL
Use descriptive text like "Read the [syllabus policy]" — not "Click here." See Links & Navigation for guidelines.
- Step 8: Set Document Properties
Fill in document title and author metadata:
File → Info → Properties → Title (enter a meaningful title)
This title is what screen readers announce when the document opens — not the file name.- Step 9: Run the Accessibility Checker
Review → Check Accessibility
Review every item in the results pane and fix all issues. The checker categorizes issues as Errors (must fix) and Warnings (should review).
Common Issues & Fixes
| Issue | How to Fix |
|---|---|
| Missing alt text | Right-click image → Edit Alt Text → write description or mark as decorative |
| Headings not using styles | Select text → apply Heading 1/2/3 from Styles pane |
| Manual list formatting | Remove typed bullets/numbers → apply Bullets or Numbering tool |
| Low contrast text | Change text or background color to meet 4.5:1 ratio |
| Tables without headers | Select table → Table Design → check Header Row |
| "Click here" link text | Edit the link — replace with descriptive text |
| Multiple H1s | Change all but one to H2 |
| Missing document title | File → Info → Properties → enter Title |
| Skipped heading levels | Fix the hierarchy so levels go in order (H1→H2→H3) |
Converting Word to PDF
Accessible Word documents export as accessible PDFs — but only if you use the right method. Never use "Print to PDF" — the result is an image file, and a completely inaccessible document!
| ✅ Do This | ❌ Don't Do This |
|---|---|
| File → Save As → PDF | File → Print → Save as PDF ("Print to PDF") |
| Preserves heading structure, alt text, and tags | Strips accessibility tags and structure |
After exporting, open the PDF in Acrobat Pro and run the Accessibility Check to confirm everything transferred correctly. See the PDF Documents Guide for details.
Checking Your Work: Complete Checklist
[ ] Document language is set
[ ] One H1 (document title); headings in order (H1→H2→H3)
[ ] All meaningful images have alt text; decorative images marked as decorative
[ ] Lists use built-in Bullets/Numbering tools
[ ] Tables have header rows; no merged cells
[ ] Color contrast meets 4.5:1 (normal text) or 3:1 (large text)
[ ] Link text is descriptive (no "click here" or raw URLs)
[ ] Document title set in Properties
[ ] Accessibility Checker run — all issues fixed