Accessibility · Product
Why accessibility does not end with a checklist
Automated checks identify some errors, but interface quality is defined by real user journeys.
It is tempting to treat accessibility as a list of requirements: add alternative text, check contrast and label every field. The list is useful, but it does not answer the main question: can a person complete the task?
A failure may not belong to one element
Every field can have a label while the form remains unusable. An error might appear at the top of the page, focus might remain on the submit button, and the screen reader may never announce what happened.
The individual elements are technically correct. The user journey is broken.
Test tasks, not only components
Define scenarios such as finding a plan, registering, paying, downloading a document or changing account details. Complete each scenario with a keyboard, a screen reader, zoom and a narrow viewport.
A checklist keeps details from being forgotten. User testing shows whether the product works as a whole.