accessibility-review
Skill4 starsChanged 3 months agoMITView on GitHub
Audit against WCAG 2.1 AA across perceivable, operable, understandable, robust. Use when accessibility, a11y, WCAG, contrast, screen reader, tap target, or is this accessible.
19 other projects use a version of this.
Adopted by
Most recently taken up by
- Vujavujavuja/Stillmotion-onbrandtheir own version, first seen Nov 16, 2026
- samsam007b/claude-code-standards-kittheir own version, first seen Nov 16, 2026
- WilliamEbong/CourseForgetheir own version, first seen Nov 8, 2026
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- toribryan/design-skillstheir own version, first seen Oct 25, 2026
- shayan-m81/layerwrighttheir own version, first seen Oct 13, 2026
Used with
Projects with it also use frontend-design.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
BlockSkillfrontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Also in 4 projects that use this
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- anthropics/knowledge-work-plugins★ 36ksame name
- markmead/hyperui★ 12ksame name
- ThibautBaissac/rails_ai_agents★ 665same name
- shayan-m81/layerwright★ 8same name
- francogalfre/skills★ 3same name
- ChloeVPin/open-agent-skills★ 2same name
- ethicalcapital/skills★ 2same name
- gvago/unofficial-qodo-review-skills★ 2same name
- loganware05/captains-compass-cursor★ 2same name
- navikt/hovmester★ 2same name
9 more not listed
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 repository46 other files it gives its agents.
- accessibility-runtime-auditSkill
- adaptive-component-behaviorSkill
- ai-feature-ux-patternsSkill
- behavioral-pricing-psychologySkill
- business-model-readingSkill
- business-model-thinkingSkill
- cognitive-load-heatmap-predictionSkill
- component-style-guideSkill
- cross-functional-reviewSkill
- dark-mode-theming-systemSkill
- dashboard-layout-patternsSkill
- dashboard-scaffolding-contractSkill
- design-drift-detectorSkill
- design-system-builderSkill
- design-to-code-handoffSkill
- design-tokensSkill
- error-boundary-resilience-designSkill
- flow-based-functional-testingSkill
- growth-impact-reviewSkill
- i18n-localization-strategySkill
- information-architectureSkill
- interactive-element-auditSkill
- kinematic-motion-choreographySkill
- micro-interaction-motion-designSkill
- module-registry-syncSkill
- mvp-scopingSkill
- perceived-performance-loadingSkill
- prd-traceability-matrixSkill
- product-discoverySkill
- product-strategySkill
- project-health-diagnosticsSkill
- qa-feedback-loop-orchestratorSkill
- responsive-breakpoint-strategySkill
- responsive-qa-auditSkill
- route-integrity-checkerSkill
- security-privacy-reviewSkill
- stakeholder-requirement-mappingSkill
- touch-gesture-interactionSkill
- typography-systemSkill
- usability-heuristics-checkSkill
- user-flow-mappingSkill
- user-research-synthesisSkill
- ux-chaos-monkeySkill
- visual-hierarchy-reviewSkill
- visual-responsive-regression-testingSkill
- visual-style-extractorSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
4
Distinctive
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 12
Non-text content: Every image, icon, and chart has alt text or aria-label.
- Distinctive: line 16
Keyboard navigation: Every interactive element is reachable via Tab and activatable via Enter/Space.
- Distinctive: line 22
Labels: Every form input has a visible label (not just placeholder text).
- Very specific: line 28
Semantic HTML: Use <button> for actions, <a> for navigation, <nav>, <main>, <header>, <footer> for landmarks.
- Distinctive: line 29
ARIA: Use ARIA roles/properties only when semantic HTML is insufficient.
“Common” is measured: kept by at least 6 in 10 of the 16 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 is a Constraint, Not a Checkbox
Accessibility is not a checkbox at the end — it's a constraint from the start. Every inaccessible element is a user you've locked out. Audit against WCAG 2.1 AA as the baseline; anything less is a known risk.
1. Perceivable
- Color contrast: Text against background meets 4.5:1 for normal text, 3:1 for large text. Check every color pairing in the design tokens.
- Non-text content: Every image, icon, and chart has alt text or aria-label.
- State indicators: Color is not the sole indicator of state (error = red + icon + text, not just red).
2. Operable
- Keyboard navigation: Every interactive element is reachable via Tab and activatable via Enter/Space. Tab order follows visual order.
- Focus indicators: Visible focus ring on every focusable element. Never
outline: nonewithout a replacement. - Tap targets: Minimum 44×44px on touch devices.
- No keyboard traps: Modals, dropdowns, and popovers must allow escape via Esc.
3. Understandable
- Labels: Every form input has a visible label (not just placeholder text).
- Error messages: Specific ("Email must contain @"), not generic ("Invalid input").
- Language: Page declares
langattribute. - Predictable: Similar things behave similarly across the product.
4. Robust
- Semantic HTML: Use
<button>for actions,<a>for navigation,<nav>,<main>,<header>,<footer>for landmarks. - ARIA: Use ARIA roles/properties only when semantic HTML is insufficient.
- Heading hierarchy:
h1→h2→h3, no skipping levels.
Output Format
- Accessibility audit checklist: criterion → pass/fail → evidence → fix recommendation.
- Summary: total pass, total fail, severity of failures.
Completion Criteria
Done when every criterion in the 4 categories has been evaluated. Not done if "we'll check accessibility later."
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.

