Start from user tasks

Before choosing a tool or writing more code, make the requirement concrete. Registration must work without sight, without a mouse, with zoom, with reduced motion, and with clear error recovery.

Accessibility work begins with people and tasks, then uses standards and tools to find barriers. The useful target is not encyclopedic coverage. Make one deliberate choice, observe its consequences, and know which requirement would make you revise it.

A common failure is to treat accessibility as a final score or a checklist for one imaginary user. The happy path may still work, which makes the mistake easy to miss. write critical tasks, varied interaction conditions, and observable success criteria before auditing components. Keep the first version small enough that every important input and output remains visible.

This supports the module goal: Frame accessibility around successful user tasks and inspect what browsers expose to assistive technology. Capture the request, command, trace, screenshot, test result, or other evidence that proves the result.

Describe the complete registration task for keyboard-only, screen-reader, low-vision, and cognitive-load scenarios. Change one condition on purpose, predict the result, and compare the prediction with what actually happened.