Article: Reviewing a design for accessibility
Description
A short checklist to use when reviewing a design for accessibility (to help designers), and ideas for annotating it (to help developers).
Probably these things:
- The page title is unique and describes page content.
- All images (including icons) have alt text.
- Headings are used liberally and no levels are skipped.
- Links or buttons with the same text, repeated on a page have a longer accessible name that's unique (e.g. 'View details of Quarterly review Q1' instead of just 'View details').
- Groups of related forms controls (e.g. multiple choice, data selector) have a name (visible or not) that provides context for the individual questions in the group (e.g. a legend).
- Form controls (one input plus one label) have a name (visible or not).
- Any error messages are clear and helpful.
- Standard controls are much better for accessibility.
(I've previously posted this to my current employer's public dev docs)
Would you like to write the article or request that it be written?
I would like to write it :)