How to use the Accessibility User Story Generator.
Accessibility requirements should describe observable interaction behavior. Use the relevant supplied criteria and include how the behavior will be checked.
Make the workflow fit your task.
Describe the interaction outcome for the relevant access need and attach observable acceptance checks. Include focus, control names or other required behavior where applicable, then verify the implementation with the appropriate testing method.
- What you provide
- Interface scenario and supplied accessibility criteria.
- What you get
- Implementation-focused accessibility requirements.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Draft a keyboard-accessibility user story for a dialog. Opening moves focus inside; a labeled close action is keyboard-operable; closing returns focus to the opener. Include acceptance checks.
Completed example
Story: As a keyboard user, I want to open, use and close the dialog without losing my place. Acceptance checks: - Opening the dialog places focus on a sensible element inside it. - The close control has an understandable accessible name and works from the keyboard. - Closing returns focus to the control that opened the dialog. Verification: exercise these behaviors in the implemented interface; this draft alone does not establish conformance.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Can an accessibility user story replace testing?
No. It defines expected behavior and checks. Actual keyboard, assistive-technology or other relevant testing is needed to evaluate the implementation.
Why does a requirement such as make it accessible remain hard to verify?
Name the interaction and observable result, such as returning focus to the opener after closing a dialog.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑