accessibility-quality
Skill1 starsChanged 54 days agoMITView on GitHub
Ship UI that works with keyboard and assistive technology: semantic HTML and native controls first, ARIA only to supplement, logical focus order with visible focus and escape paths, programmatic labels and error association, contrast and non-color meaning, alt text, reduced motion, zoom and reflow. Use for any user-facing UI change and for WCAG audits; never knowingly ship an accessibility regression.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- AL-JANEF/janefskillsword for word, first seen Sep 19, 2026
Other versions1 project uses a version of this.
Word for word · 1
- AL-JANEF/janefskills★ 1100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- janefSkill
- forgeSkill
- api-contractsSkill
- architecture-integritySkill
- context-efficiencySkill
- database-integritySkill
- delegation-disciplineSkill
- devops-reliabilitySkill
- documentation-integritySkill
- frontend-design-qualitySkill
- git-disciplineSkill
- implementation-qualitySkill
- performance-scalabilitySkill
- review-defect-firstSkill
- root-cause-debuggingSkill
- testing-verificationSkill
- ui-ux-qualitySkill
- auth-hardeningSkill
- secrets-guardSkill
- security-auditSkill
- security-loggingSkill
- skill-security-auditSkill
- threat-modelSkill
- variant-huntSkill
- vuln-auditSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
Every input has a programmatic label.
- Distinctive: line 22
Do not convey meaning by color alone.
- Very specific: line 25
Check headings, landmarks, tables, names/roles/states, and touch targets on the changed surface.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Accessibility Quality
Accessibility is a correctness requirement for user-facing UI, not a polish step. Never knowingly ship an accessibility regression.
Rules
- Semantic HTML and native controls first. ARIA supplements semantics; it does not replace a correct element.
- Keyboard access for everything interactive: logical focus order, visible focus, focus return after dialogs, and an escape path for overlays and traps.
- Every input has a programmatic label. Errors and status messages are associated with their field and announced.
- Do not convey meaning by color alone. Check contrast for text and non-text indicators.
- Meaningful images get meaningful alternative text; decorative images stay out of the accessibility tree.
- Respect reduced motion, zoom and text scaling, and responsive reflow.
- Check headings, landmarks, tables, names/roles/states, and touch targets on the changed surface.
Verification
A keyboard-only pass of the changed surface; names, roles, states, and contrast checked for changed controls; a screen-reader or automated check (for example axe) where available. Report what was checked and what was not.
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.