accessible-combobox-and-autocomplete
Skill8 starsChanged 2 months agoMITView on GitHub
1. Identify editable versus select-only behavior and whether a native select meets the actual requirement. Read the combobox review guide for the selected variant. 2. Inventory closed/open, loading, results, empty, error, selected, and cleared states. Document focus, active option, committed value, and keyboard behavior separately. 3. Replay typing, option navigation, acceptance, Escape, Tab, and rapid request changes. Verify that active references identify current options and normal text editing remains available. 4. Repair state ownership and semantics together. Add tests for…
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-component-reviewSkill
- accessible-data-tables-and-gridsSkill
- accessible-dynamic-updatesSkill
- accessible-formsSkill
- dialog-accessibilitySkill
- fix-accessibility-issueSkill
- keyboard-navigation-reviewSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 28
Follow the guide's manual checks for screen-reader state announcements, editing, and mobile input.
≈ “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 combobox and autocomplete
Workflow
- Identify editable versus select-only behavior and whether a native select meets the actual requirement. Read the combobox review guide for the selected variant.
- Inventory closed/open, loading, results, empty, error, selected, and cleared states. Document focus, active option, committed value, and keyboard behavior separately.
- Replay typing, option navigation, acceptance, Escape, Tab, and rapid request changes. Verify that active references identify current options and normal text editing remains available.
- Repair state ownership and semantics together. Add tests for out-of-order results, selection correctness, dismissal, and the supported keyboard path.
- Follow the guide's manual checks for screen-reader state announcements, editing, and mobile input.
Boundaries
A listbox popup is one variant; tree, grid, and dialog popups have different responsibilities. Do not paste a listbox keyboard model onto all variants. General form errors remain in accessible-forms; this skill owns suggestion and selection behavior.
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.

