accessibility-checker
Skill0 starsChanged 7 months agoMITView on GitHub
Check HTML pages for accessibility issues and WCAG 2.1 AA compliance. Automatically loads when working on HTML accessibility, ARIA labels, or screen reader compatibility.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- peopleforrester/claude-dotfilestheir own version, first seen Apr 5, 2026
- SRMaison999/claude-agents-skillstheir own version, first seen Nov 5, 2025
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- peopleforrester/claude-dotfiles★ 3same name
- SRMaison999/claude-agents-skills★ 1same 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 repository5 other files it gives its agents.
- code-documentationSkill
- code-reviewSkill
- form-validatorSkill
- nextjs-frontendSkill
- ux-motionSkill
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 86
When reviewing a file, check for:
≈ “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 Checker Skill
This skill provides guidance for checking and improving web accessibility.
WCAG 2.1 AA Checklist
Perceivable
- All images have meaningful
alttext - Videos have captions/transcripts
- Color is not the only way to convey information
- Text has sufficient contrast ratio (4.5:1 normal, 3:1 large)
- Content is readable at 200% zoom
Operable
- All functionality available via keyboard
- No keyboard traps
- Skip links for navigation
- Focus indicators visible
- Touch targets at least 44x44px
- Page titles are descriptive
Understandable
- Language is declared (
<html lang="en">) - Error messages are clear and helpful
- Labels are associated with form inputs
- Navigation is consistent across pages
Robust
- Valid HTML structure
- ARIA attributes used correctly
- Works with assistive technologies
Common Issues to Check
Images
<!-- Bad -->
<img src="logo.png" />
<!-- Good -->
<img src="logo.png" alt="NovaTech Solutions logo" />
<!-- Decorative (empty alt is intentional) -->
<img src="decoration.png" alt="" aria-hidden="true" />Forms
<!-- Bad -->
<input type="email" placeholder="Email" />
<!-- Good -->
<label for="email">Email</label>
<input type="email" id="email" aria-describedby="email-hint" />
<span id="email-hint">We'll never share your email</span>Navigation
<!-- Include skip link -->
<a href="#main-content" class="skip-link">Skip to main content</a>
<!-- Use landmarks -->
<nav aria-label="Main navigation">
<ul>
<li><a href="/">Home</a></li>
<li><a href="/about">About</a></li>
</ul>
</nav>Automated Checks
When reviewing a file, check for:
- Missing
altattributes on images - Empty links or buttons
- Missing form labels
- Missing language declaration
- Missing landmark regions
- Improper heading hierarchy (h1 → h2 → h3)
- Missing ARIA labels on icon-only buttons
Output Format
## Accessibility Review: [filename]
### Critical Issues
- [Issue description] (Line X)
### Warnings
- [Issue description] (Line X)
### Passed Checks
- ✓ [What's done correctly]
### Recommendations
- [Suggestion for improvement]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.

