agentleFS
Sign inStart free
d-o-hubd-o-hub/github-template-ai-agents/.agents/skills/accessibility-auditor/SKILL.md

accessibility-auditor

Skill2 starsChanged 11 days agoMITView on GitHub

Audit web applications for WCAG 2.2 compliance, screen reader compatibility, keyboard navigation, and color contrast. Use this skill when the user asks for an accessibility audit, a11y check, WCAG compliance review, screen reader test, keyboard navigation check, color contrast check, or ARIA validation — even if they don't explicitly mention "accessibility" or "WCAG". Also triggers on Section 508 and ADA compliance requests. Not for css-render-performance.

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 3

    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
  1. Distinctive:

    Check these automatically using axe-core, Lighthouse, or WAVE:

    line 25
  2. Distinctive:

    Keyboard: Verify Tab order and focus indicators (2.4.7).

    line 34
  3. Distinctive:

    Zoom: Test reflow at 400% zoom (1.4.10).

    line 35

“Common” is measured: kept by at least 6 in 10 of the 9 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Accessibility Auditor

Audit web applications for WCAG 2.2 compliance, screen reader compatibility, keyboard navigation, and color contrast issues.

When to Use

  • User asks for an accessibility audit or a11y check
  • Reviewing WCAG 2.2 compliance or Section 508/ADA requirements
  • Testing screen reader compatibility or keyboard navigation
  • Checking color contrast or ARIA validation
  • Even if they just say "is this accessible" or "check for accessibility issues"

Audit Workflow

Phase 1: Automated Scan

Check these automatically using axe-core, Lighthouse, or WAVE:

  • Color contrast (1.4.3)
  • Missing alt text (1.1.1)
  • Form labels (3.3.2)
  • Heading hierarchy (1.3.1)

Phase 2: Manual Testing

  • Screen Reader: Navigate with NVDA/VoiceOver/JAWS arrow keys.
  • Keyboard: Verify Tab order and focus indicators (2.4.7).
  • Zoom: Test reflow at 400% zoom (1.4.10).

Severity Classification

SeverityImpactPriority
CriticalBlocks accessFix immediately
HighSignificant barrierFix before release
MediumMinor frictionNext sprint
LowEnhancementBacklog

See Also

  • css-render-performance — CSS render performance optimization
  • ui-ux-optimize — UI/UX optimization with swarm agents

Rationalizations

RationalizationReality
"Automated scans catch everything"Automated tools miss keyboard traps, focus order, screen reader semantics, and cognitive load issues.
"Accessibility only matters for blind users"Motor, cognitive, and situational impairments affect far more users than visual alone.
"We'll fix accessibility in the next release"Each release without a11y compounds legal risk and excludes users; fix forward.

Red Flags

  • Only automated scans run without manual keyboard/screen reader testing
  • Color contrast issues deferred as cosmetic
  • ARIA labels applied without role verification

References

  • Accessibility Checklist - Complete WCAG 2.2 criteria and testing procedures.
  • references/aria-guide.md - ARIA authoring practices
  • references/screen-reader-testing.md - Testing procedures
  • references/color-contrast.md - Contrast calculations

Voice & Context

  • Default: professional + blog
  • Reference: voice-profiles skill for definitions and auto-detection.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free