accessibility-a11y
Skill0 starsChanged 4 months agoMITView on GitHub
Build inclusive, WCAG-compliant UIs. Use for a11y, screen readers, ARIA, keyboard nav, contrast, or accessibility audits.
8 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- manish1803/nextjs-fullstack-skillstheir own version, first seen Oct 13, 2026
- Mindrally/skillsedited, first seen Oct 8, 2026
- ZeroTokenClaw/agents-skillsedited, first seen Sep 21, 2026
- novatic-cu/nova-skillstheir own version, first seen Sep 20, 2026
- seven-hills-software/skillwright-skillstheir own version, first seen Jun 23, 2026
- web-werkstatt/claude-code-workflowedited, first seen Apr 28, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 4
- Mindrally/skills★ 27511% same
- ZeroTokenClaw/agents-skills★ 111% same
- JasonPaff/clarify★ 011% same
- web-werkstatt/claude-code-workflow★ 011% same
Wrote their own version · 4
- travisjneuman/.claude★ 106same name
- manish1803/nextjs-fullstack-skills★ 2same name
- novatic-cu/nova-skills★ 1same name
- seven-hills-software/skillwright-skills★ 0same name
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 repository63 other files it gives its agents.
- .claude/skills/nestjs-best-practices/AGENTS.mdAGENTS.md
- architecture-blueprint-generatorSkill
- backend-delivery-loopSkill
- backend-designSkill
- backend-dev-guidelinesSkill
- backend-testingSkill
- backend-to-frontend-handoff-docsSkill
- building-componentsSkill
- bullmq-specialistSkill
- canvas-designSkill
- code-patternsSkill
- components-composition-patternsSkill
- conventional-commitSkill
- core-web-vitalsSkill
- create-svgSkill
- css-architectureSkill
- cypress-authorSkill
- cypress-docsSkill
- cypress-explainSkill
- delivery-loop-retroSkill
- diagnoseSkill
- fastify-best-practicesSkill
- figma-code-connectSkill
- frontend-delivery-loopSkill
- frontend-fundamentalsSkill
- fullstack-delivery-loopSkill
- grill-meSkill
- hunt-race-conditionSkill
- impeccableSkill
- mermaid-diagramsSkill
- nestjs-best-practicesSkill
- nextjs-best-practicesSkill
- nextjs-performanceSkill
- nodejs-backend-patternsSkill
- owasp-security-reviewSkill
- performance-hunterSkill
- playwright-best-practicesSkill
- postgresql-code-reviewSkill
- postgresql-optimizationSkill
- postmanSkill
- prisma-postgresSkill
- pro-state-machineSkill
- race-conditionSkill
- react-best-practicesSkill
- react-performanceSkill
- react-querySkill
- redis-coreSkill
- redis-query-engineSkill
- redis-securitySkill
- refactorSkill
- review-panelSkill
- run-delivery-chainSkill
- spec-drivenSkill
- sql-optimizationSkill
- system-designSkill
- testing-strategySkill
- tune-skills-and-agentsSkill
- ui-ux-pro-maxSkill
- vercel-react-view-transitionsSkill
- viteSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
4
Distinctive
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 12
Follow WCAG (Web Content Accessibility Guidelines) standards
- Distinctive: line 13
Use semantic HTML to improve accessibility and screen reader compatibility
- Distinctive: line 14
Ensure high accessibility standards using ARIA roles and native accessibility props
- Distinctive: line 16
Test with various assistive technologies
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Accessibility (a11y) Best Practices
You are an expert in web accessibility and inclusive design. Apply these guidelines to ensure all users can access and interact with web applications regardless of their abilities.
Core Accessibility Principles
- Follow WCAG (Web Content Accessibility Guidelines) standards
- Use semantic HTML to improve accessibility and screen reader compatibility
- Ensure high accessibility standards using ARIA roles and native accessibility props
- Design for all users including those with visual, auditory, motor, and cognitive disabilities
- Test with various assistive technologies
References
Each file is loaded on demand — read one only when the task needs that depth (progressive disclosure).
references/semantic-aria.md— semantic HTML (structural elements, form accessibility) and ARIA (when to use it, common patterns) · read when authoring markup, forms, or non-native interactive widgets.references/visual-keyboard.md— visual accessibility (color, contrast, focus management) and keyboard navigation (requirements, interactive elements, touch targets) · read when styling visuals/focus or making interactions keyboard-operable.references/content-responsive.md— content accessibility (images, media, text, typography) and responsive/adaptive design (mobile-first, user preferences likeprefers-reduced-motion) · read when handling images/media/copy or building responsive, preference-aware layouts.references/testing-css.md— testing & validation (automated tools, manual/screen-reader testing) and CSS best practices for accessibility · read when auditing/validating a11y or setting up styling conventions.
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.

