Test the journey rather than a single button
The original synthetic task is to search available bookings, select one, submit a request and correct a missing required field using a keyboard. The expected behaviour below is a buyer-defined task pack, not a complete accessibility standard.
| Task stage | Input/action | Expected observation | Evidence requested |
|---|---|---|---|
| Find a slot | Keyboard reaches labelled search and results | Visible focus; understandable result names | Focus route and selected result |
| Submit missing name | Reach submit, then receive validation | Error identifies name field and provides a route back | Error text and focus position |
| Correct and finish | Fill name; submit once | Request status is reachable; no keyboard trap | Final state and navigation route |
A reachable button does not prove a usable task
Submit is keyboard-reachable, but the validation message cannot be reached or associated with a field. Does the fixture pass?
Show the worked answer
No. The missing-name and correction stages are part of the agreed journey. Record that gap and retest the full route after repair.
This sheet does not claim WCAG conformance or assess every assistive technology. Define the actual devices, browsers and additional review needed before making an accessibility claim.