dialog-accessibility
Skill8 starsChanged 2 months agoMITView on GitHub
Verify the whole open–operate–close lifecycle. 1. Decide whether native <dialog> meets the product behavior before retaining a custom dialog. 2. Open it from a known invoker and apply references/dialog-checklist.md. 3. Verify the accessible name and any useful description, deliberate initial focus, containment for a modal, background inertness, keyboard-operable close control, Escape behavior, and restoration to the logical invoker. 4. Test close by every offered path and test DOM removal or route changes that invalidate the invoker. 5. Replay at mobile…
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessibility-auditSkill
- accessibility-regression-testSkill
- accessible-authenticationSkill
- accessible-charts-and-dashboardsSkill
- accessible-combobox-and-autocompleteSkill
- accessible-component-reviewSkill
- accessible-data-tables-and-gridsSkill
- accessible-dynamic-updatesSkill
- accessible-formsSkill
- fix-accessibility-issueSkill
- keyboard-navigation-reviewSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Verify the whole open–operate–close lifecycle.
- Distinctive: line 23
Verify the accessible name and any useful description, deliberate initial focus, containment for a modal, background inertness, …
- Distinctive: line 26
Test close by every offered path and test DOM removal or route changes that invalidate the invoker.
- Very specific: line 35
Do not force focus to the first interactive control when a heading or explanatory content is the more useful starting point.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Dialog accessibility
Verify the whole open–operate–close lifecycle.
Workflow
- Decide whether native
<dialog>meets the product behavior before retaining a custom dialog. - Open it from a known invoker and apply references/dialog-checklist.md.
- Verify the accessible name and any useful description, deliberate initial focus, containment for a modal, background inertness, keyboard-operable close control, Escape behavior, and restoration to the logical invoker.
- Test close by every offered path and test DOM removal or route changes that invalidate the invoker.
- Replay at mobile width and high zoom. Assess nested dialogs as a separate high-risk interaction.
- Save a bounded keyboard journey and rerun the relevant deterministic scan after repairs.
Boundaries
Do not force focus to the first interactive control when a heading or
explanatory content is the more useful starting point. Do not add role=dialog
without implementing the interaction model. A passing axe scan does not prove
containment, restoration, or mobile usability.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

