accessible-forms
Skill8 starsChanged 2 months agoMITView on GitHub
Review the user journey, not isolated inputs. 1. Identify every available state: initial, invalid submission, corrected input, and successful submission. Test at least initial, invalid, and successful states when they exist. 2. Apply references/forms-checklist.md to labels, instructions, required communication, autocomplete, grouping, and authentication. 3. Submit invalid data. Verify errors are identified in text, programmatically connected to fields, announced or focused appropriately, and summarized when the form size warrants it. 4. Correct the form and verify stale error state is removed…
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
- 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 30
Prefer native form elements and associations.
- Distinctive: line 37
Do not invent labels, requirements, validation copy, autocomplete purpose, or authentication policy.
≈ “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 forms
Review the user journey, not isolated inputs.
Workflow
- Identify every available state: initial, invalid submission, corrected input, and successful submission. Test at least initial, invalid, and successful states when they exist.
- Apply references/forms-checklist.md to labels, instructions, required communication, autocomplete, grouping, and authentication.
- Submit invalid data. Verify errors are identified in text, programmatically connected to fields, announced or focused appropriately, and summarized when the form size warrants it.
- Correct the form and verify stale error state is removed without losing needed instructions.
- Prefer native form elements and associations. Add live regions only for dynamic changes that need announcement; avoid duplicate announcements.
- Preserve the deterministic scan and interaction evidence, then add a user-behavior regression test.
Boundaries
Do not invent labels, requirements, validation copy, autocomplete purpose, or authentication policy. Escalate missing product meaning for human decision. A machine-detectable label does not establish that the label is clear or correct.
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.

