accessible-dynamic-updates
Skill8 starsChanged 2 months agoMITView on GitHub
1. List the initiating action, update type, loading/error/completion states, and the user's expected next task. 2. Use the dynamic update guide to decide whether to move focus, expose a passive status, or leave an ordinary content update alone. 3. Observe focus and live-region mutations during the entire sequence, including rapid updates, cancellation, retry, and stale responses. Do not infer speech from attributes. 4. Repair the responsible state/announcement logic. Add tests for preserved focus, relevant completion feedback, and superseded or cancelled…
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-formsSkill
- dialog-accessibilitySkill
- fix-accessibility-issueSkill
- keyboard-navigation-reviewSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Use the dynamic update guide to decide whether to move focus, expose a passive status, or leave an ordinary content update alone.
- Distinctive: line 26
Run the guide's manual screen-reader procedure to assess timing, duplication, interruption, and reading continuity.
≈ “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
Accessible dynamic updates
Workflow
- List the initiating action, update type, loading/error/completion states, and the user's expected next task.
- Use the dynamic update guide to decide whether to move focus, expose a passive status, or leave an ordinary content update alone.
- Observe focus and live-region mutations during the entire sequence, including rapid updates, cancellation, retry, and stale responses. Do not infer speech from attributes.
- Repair the responsible state/announcement logic. Add tests for preserved focus, relevant completion feedback, and superseded or cancelled work.
- Run the guide's manual screen-reader procedure to assess timing, duplication, interruption, and reading continuity.
Boundaries
Generic component semantics remain in accessible-component-review. This skill owns temporal behavior across states. Do not make every changing subtree live, use assertive alerts for all updates, or claim that a mutation trace proves a screen reader announced it.
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.

