Goal
Prompt for accessibility with concrete tasks and observable checks rather than a generic request to be compliant.
Step-by-step
- Specify semantic controls.
- include keyboard paths.
- test dynamic updates.
- involve assistive-technology checks.
Worked scenario
Ask for an error summary that moves focus to the invalid input.
Write down the current behavior, the intended change, and the evidence you would need before deciding it worked. Use synthetic or anonymized material for exploration.
Acceptance check
Claims of accessibility are supported by real checks and remaining gaps.
Common failure
A convincing artifact can hide untested assumptions. Keep an explicit list of unknowns and test the highest-consequence transition before expanding the work.
Next step
Apply the guide to one bounded task, review the evidence, and adjust the approach. The linked reference is a separate publication; this guide is Knoveya's independent treatment of the topic.