agentleFS
Sign inStart free
NikoxkxNikoxkx/Agent-Skills/skills/web-development/accessibility-auditor/SKILL.md

accessibility-auditor

Skill1 starsChanged 5 months agoApache-2.0View on GitHub

Audits web interfaces for WCAG 2.1 AA compliance and generates a prioritized fix list. Use when auditing accessibility, preparing for legal compliance, or improving inclusivity.

10 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. 0 are common, 15 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 15

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

    Before launching a new feature or site.

    line 19
  2. Distinctive:

    After a design or code change that affects UI.

    line 20
  3. Very specific:

    Run axe-core (browser extension or axe-core in CI).

    line 34
  4. Distinctive:

    Run Lighthouse Accessibility category.

    line 35
  5. Distinctive:

    Run WAVE (webaim.org/wave).

    line 36
  6. Distinctive:

    Verify visible focus indicators on every interactive element.

    line 41
  7. Distinctive:

    Test all functionality (modals, dropdowns, carousels, forms) with keyboard only.

    line 42
  8. Distinctive:

    Check skip links, logical tab order, and no keyboard traps.

    line 43
  9. Distinctive:

    Use VoiceOver (Mac) or NVDA.

    line 46
  10. Distinctive:

    Verify headings are logical (H1 → H2 etc.).

    line 48
  11. Distinctive:

    Check that images have alt text, form labels are announced, ARIA live regions work, and dynamic content is announced.

    line 49
  12. Distinctive:

    Test with rotor/landmarks.

    line 50
  13. Distinctive:

    Check all text and non-text (icons, buttons) against 4.5:1 (text) / 3:1 (large text, UI components).

    line 53
  14. Distinctive:

    Test in both light and dark modes if applicable.

    line 54
  15. Distinctive:

    Before/after code snippets for top issues.

    line 78
  16. Distinctive:

    Dynamic content: Ensure live regions and focus management on updates.

    line 89

“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

Overview

Performs a thorough accessibility audit against WCAG 2.1 AA (and notes AAA where relevant). Combines automated tools (axe-core, WAVE, Lighthouse), manual testing procedures (keyboard-only navigation, screen reader simulation, zoom, color contrast), common ARIA misuse patterns, and produces a prioritized fix list with severity, effort, and concrete remediation steps.

When to Use This Skill

  • Before launching a new feature or site.
  • After a design or code change that affects UI.
  • User requests an "accessibility audit", "a11y review", "WCAG compliance", or "make it accessible".
  • Legal or procurement requirements (Section 508, ADA, etc.).

Prerequisites

  • The live page or a deployed preview.
  • Browser DevTools + axe DevTools extension (or CLI).
  • Screen reader (VoiceOver on Mac, NVDA on Windows — free).
  • Color contrast tool (WebAIM or built into DevTools).

Steps

  1. Automated scan:
    • Run axe-core (browser extension or axe-core in CI).
    • Run Lighthouse Accessibility category.
    • Run WAVE (webaim.org/wave).
    • Record all violations with node selectors or screenshots.
  2. Manual keyboard test:
    • Tab through the entire page.
    • Verify visible focus indicators on every interactive element.
    • Test all functionality (modals, dropdowns, carousels, forms) with keyboard only.
    • Check skip links, logical tab order, and no keyboard traps.
  3. Screen reader test:
    • Use VoiceOver (Mac) or NVDA.
    • Listen to the page reading order.
    • Verify headings are logical (H1 → H2 etc.).
    • Check that images have alt text, form labels are announced, ARIA live regions work, and dynamic content is announced.
    • Test with rotor/landmarks.
  4. Color & contrast:
    • Check all text and non-text (icons, buttons) against 4.5:1 (text) / 3:1 (large text, UI components).
    • Test in both light and dark modes if applicable.
    • Simulate color blindness (DevTools or Coblis).
  5. WCAG 2.1 AA checklist (structured by POUR):
    • Perceivable: text alternatives, captions, contrast, resize text, reflow.
    • Operable: keyboard, enough time, seizures, navigable, input modalities.
    • Understandable: readable, predictable, input assistance.
    • Robust: compatible with assistive tech, valid markup.
  6. Common ARIA pitfalls to flag:
    • aria-hidden on focusable elements.
    • Incorrect role or missing required ARIA attributes.
    • Over-use of aria-label instead of visible text.
    • tabindex > 0.
  7. Prioritized fix list:
    • Severity: Critical (blocks users), High, Medium, Low.
    • Effort estimate.
    • Exact fix (code change or design change).
    • Success criteria for re-test.
  8. Output:
    • Summary of automated + manual findings.
    • Full prioritized matrix.
    • Before/after code snippets for top issues.
    • Recommendations for ongoing monitoring (axe in CI, manual spot-checks).

Examples

A sample audit report for a typical dashboard page (with 8-10 findings across categories) and remediation code for the most common issues (missing labels, focus management in modals, color contrast, keyboard navigation in custom components) are included.

Edge Cases & Error Handling

  • Complex widgets (data tables, date pickers, rich text editors): Recommend ARIA patterns from WAI-ARIA Authoring Practices or a well-tested library (React Aria, Radix).
  • Third-party components: Audit them separately; suggest alternatives if they fail badly.
  • Dynamic content: Ensure live regions and focus management on updates.

Verification

  1. Re-run axe and Lighthouse after fixes — critical violations = 0.
  2. Perform the same keyboard + screen reader test — all flows work without assistance.
  3. Contrast checker passes for all text/UI.
  4. A real user who relies on assistive technology tests the flow (if possible).
  5. Success: WCAG 2.1 AA conformance (or as close as the design allows), with documented exceptions if any.

References

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