Theme: Preventing problems before publishing
Tip 14: File Naming & Document Metadata
Core skill: Use clear file names and titles for accessibility.
Why it matters
Screen reader users often navigate files by title, not filename. Clear naming also improves search, version control, and usability for everyone.
What to do (2-minute action)
- Use meaningful file names (e.g., ucanr-travel-policy-2026.pdf)
- Set the document title in PDF properties
- Avoid “Final_v3_REALLYFINAL.pdf”
- Google prefers that hyphens separate the words.
- This is good: " red-wagon-has-four-wheels.png"
- This is bad: "red Wagon Has Four wheels.png"
- This is bad: "675792.pdf"
Learn more
- Microsoft: Create Accessible File Names
- University of Minnesota: Add Plain Alternative Text
- UCANR Naming Conventions for the Internet
Tip 15: Accessibility Checkers (Use Them Wisely)
Core skill: Combine automated checks with human review for accessibility.
Why it matters
Accessibility checkers catch many issues—but never all of them.
What to do (5-minute action)
- Run built-in accessibility checkers (Word, Acrobat, Siteimprove)
- Review flagged issues manually
- Ask: Can this be understood without seeing it?
Key reminder
Passing a checker does not guarantee accessibility.
Learn more
- UCOP: Checking Website Accessibility with Siteimprove
- University of Minnesota ODA: Use Accessibility Checkers
- Siteimprove: Accessibility Code Checker; Accessibility Testing for the Web