Test dialog accessibility with AI
Check a dialog from its trigger to its dismissal. Follow keyboard focus, accessible naming and background behaviour through the actual modal or non-modal interaction.
Test dialog accessibility with AI when a confirmation or editor seems usable with a mouse but the keyboard path is unclear. The dialog-accessibility skill examines what opens the dialog, where focus lands, how people reach its controls and where they return afterwards. It distinguishes modal behaviour from an intentionally non-modal surface.
A delete confirmation is a useful test case. Cancelling can return focus to the original button. Confirming may remove that button with its row, so the interface needs a sensible next destination. A successful static check cannot tell you whether that handover is understandable in the running interface.
What it does
- Check a dialog’s accessible name and purpose.
- Follow initial focus after opening.
- Test forward and reverse keyboard movement.
- Check interaction with the background where relevant.
- Verify focus recovery when the original trigger disappears.
Install and use
- Install the skill and provide an authorised test dialog, a keyboard and the relevant browser or screen reader. Use disposable test data for destructive actions.
- Ask, “Review this delete confirmation from the trigger through cancel and confirm. Record the final focus destination in each case.”
- Retest the repaired component across its supported dismissal paths and record the combinations actually exercised.
FAQ
Source
Made by smukh / a11y-agent-skills contributors. Original skill: dialog-accessibility, published on GitHub under the MIT licence.
View on GitHub