About this sample
- What this is A published article on designing documentation that works for everyone, including people who use screen readers, have color vision differences or can't use a mouse.
- Audience Technical writers and documentation teams.
- Tools used Google Sites.
- What it demonstrates Knowledge of accessibility standards (WCAG, Section 508) and the ability to turn them into practical guidance for writers.
Designing documentation for accessibility
What the article covers
- What accessible documentation is, and who it serves
- Why technical writers should care: reach, trust, fewer support requests, and legal and ethical expectations
- Practical techniques: plain language, nested headings, alt text, table header rows, descriptive link text, captions and transcripts, readable fonts and contrast
- How to test documentation with free checkers
- How accessibility skills add to a writer's value