It's often easier to have a downloadable document such as a PDF on your website than to make a whole new page or section within a page. But if you have downloadable documents, how can you make them accessible for people with visual impairments?
Are PDFs more accessible than Word files
PDFs on websites can be accessible, but they often aren’t by default. Their accessibility depends on how they’re created and whether accessibility features are included. Here's a breakdown:
✅ When PDFs are accessible:
-
Proper structure: They include headings, lists, tables, and alt text for images.
-
Tagged PDFs: These contain hidden labels (tags) that help screen readers interpret content correctly.
-
Logical reading order: The content flows in a way that makes sense when read by assistive tech.
-
Selectable, searchable text: Text isn’t just an image (i.e., not scanned without OCR).
-
Proper contrast and font sizes are used.
-
Form fields are interactive and labelled clearly.
❌ Common accessibility issues:
-
Scanned PDFs without OCR (Optical Character Recognition).
-
Lack of heading structure.
-
Missing tags or improperly tagged elements.
-
Poor colour contrast or tiny fonts.
-
Complex layouts that don't linearise well for screen readers.
-
Inaccessible forms or unlabeled form fields.
🛠️ Best practices:
-
Create PDFs from accessible source documents (like Word or InDesign with accessibility settings enabled).
-
Use Adobe Acrobat Pro or similar tools to check and enhance accessibility.
-
Test with screen readers like NVDA or VoiceOver.
-
Provide an HTML alternative whenever possible — HTML is generally more accessible than PDFs.
In general, Word files (.doc or .docx) are often more accessible than PDFs, but it depends on how each file is created and used. Here's a comparison:
In general, Word files (.doc or .docx) are often more accessible than PDFs, but it depends on how each file is created and used. Here's a comparison:
🔍 Accessibility Comparison: PDF vs Word
| Feature | Word Documents | PDFs |
|---|---|---|
| Structure (headings, lists) | Easy to apply and screen-reader friendly | Requires tagging to be accessible |
| Editing | Easy to edit with Word or other apps | Requires special software like Acrobat |
| Screen Reader Support | Good support when styles are used properly | Good if properly tagged and structured |
| Forms | Limited and basic | Advanced form fields, but often inaccessible |
| Navigation | Built-in heading styles make navigation easy | Must be tagged and bookmarked manually |
| Conversion to Other Formats | Easy and retains accessibility features | Can lose accessibility during conversion |
| Distribution | Less universal; not all devices open Word by default | Universally viewable with PDF readers |
✅ Word is usually better when:
- You’re still editing or collaborating on the document.
- Your audience may use assistive tech that prefers editable text.
- You want to preserve accessibility settings easily.
✅ PDF is better when:
- You need a fixed layout for printing or branding.
- You’ve finalized the document and ensured it’s properly tagged.
- You want consistency across devices.
🔄 Best practice:
If accessibility is your goal, start with a well-structured Word document, use proper styles, then export to a tagged PDF with accessibility settings intact.
