Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A a11yproject.com
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 40
    • Issues 40
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 10
    • Merge requests 10
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The A11Y Project
  • a11yproject.com
  • Issues
  • #1327
Closed
Open
Issue created Aug 12, 2021 by Steve Barnett@SteveBarnettContributor

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:

  1. The page title is unique and describes page content.
  2. All images (including icons) have alt text.
  3. Headings are used liberally and no levels are skipped.
  4. 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').
  5. 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).
  6. Form controls (one input plus one label) have a name (visible or not).
  7. Any error messages are clear and helpful.
  8. 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 :)

Assignee
Assign to
Time tracking