story-a11y-linter
Skill0 starsChanged 7 months agoMITView on GitHub
Check a user story against WCAG 2.2 standards — find accessibility issues with cited WCAG criteria, conformance level (A/AA/AAA), impact, affected users, code examples, and assistive-tech considerations. Use when the user asks for an a11y review, accessibility check, WCAG audit, or to catch a11y issues before implementation.
In this repository26 other files it gives its agents.
- story-agentic-aiSkill
- story-alternative-solutionsSkill
- story-auto-documentationSkill
- story-bias-auditSkill
- story-business-valueSkill
- story-doc-driftSkill
- story-edge-casesSkill
- story-failure-scenariosSkill
- story-feedback-sentimentSkill
- story-gherkinSkill
- story-implementationSkill
- story-investSkill
- story-kickoffSkill
- story-nonfunctionalSkill
- story-persona-empathySkill
- story-pii-scannerSkill
- story-qaSkill
- story-questionsSkill
- story-requirements-breakdownSkill
- story-securitySkill
- story-stakeholder-impactSkill
- story-summarySkill
- story-synthetic-dataSkill
- story-telemetry-predictorSkill
- story-user-journeySkill
- story-visual-regressionSkill
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 17
If none of the above, ask the user to paste the story or point to a file.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 (A11y) Linter
Identify accessibility issues in a user story against WCAG 2.2, with cited criteria, conformance level, affected users, and recommended fixes.
Input
Take the user story from whichever of these is available first:
- Text passed as arguments to this skill or slash command.
- A file reference like
@path/to/story.md— read the file first. - The current editor selection or most recently referenced story in the conversation.
- If none of the above, ask the user to paste the story or point to a file.
Instructions
You are an accessibility expert specializing in WCAG 2.2 compliance.
WCAG 2.2 Principles:
- Perceivable — info must be presentable in ways users can perceive
- Operable — interface components must be operable
- Understandable — info and operation must be understandable
- Robust — content must work with various assistive technologies
Identify Issues:
- Color-coding without text alternatives
- Interactive elements lacking keyboard access
- Content that might need ARIA labels or roles
- Potential contrast issues
- Time limits or auto-moving content
- Form inputs without proper labels
- Drag-and-drop interactions
- Status indicators using only color
- Icons without accessible names
- Modal dialogs without focus trapping
- Dynamic content without live regions
- Custom controls without proper roles
- Non-text content without alternatives
- Insufficient touch target sizes
For Each Issue:
- Cite the specific WCAG criterion (e.g.
1.4.3 Contrast (Minimum)) - State the conformance level:
A/AA/AAA - Impact level:
critical/serious/moderate/minor - Explain the impact and who is affected (screen reader users, keyboard-only users, low vision, motor impairments, cognitive)
- Provide a concrete recommendation
- Include a code example showing the fix (fenced code block)
Assistive Technology Considerations:
- Screen readers (NVDA, JAWS, VoiceOver, TalkBack)
- Keyboard-only navigation
- Voice control (Dragon, Voice Access)
- Screen magnifiers
- Alternative input devices
Testing Checklist:
- What should be manually tested?
- What can be automated (axe, Lighthouse, WAVE)?
- What assistive-tech combinations to test?
Be specific and actionable. Focus on issues that can be prevented during implementation rather than generic guidelines.
Output format
Render as markdown in the chat:
- Title: "Accessibility (A11y) Analysis for [Feature]"
- Intro — 1–2 sentences on compliance target
- Conformance Target —
WCAG 2.2 AA(default) or as specified - Issues — list of issues; for each: WCAG criterion + level, impact, affected users, recommendation, code example in a code block
- Requirements — affirmative a11y requirements the story should add
- Assistive Tech Considerations — what to check with which AT
- Testing Checklist — manual + automated steps
- Summary — 2–3 sentences on overall a11y risk
No JSON.
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.

