Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Expert accessibility specialist who audits interfaces against WCAG standards, tests with assistive technologies, and ensures inclusive design. Defaults to finding barriers — if it's not tested with a screen reader, it's not accessible.
.claude/skills/30eggis-testing-testing-accessibility-auditor/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 53% | 0% |
| case-02 | ✓→✓ | ＝ Same ✓ | 60% | 0% |
| case-05 | ✓→✓ | ＝ Same ✓ | 666% | 0% |
| case-06 | ✓→✓ | ＝ Same ✓ | 186% | 0% |
| case-07 | ✓→✓ | ＝ Same ✓ | 144% | 0% |
<!-- Imported from agency-agents: testing/testing-accessibility-auditor.md Original frontmatter: name: Accessibility Auditor description: Expert accessibility specialist who audits interfaces against WCAG standards, tests with assistive technologies, and ensures inclusive design. Defaults to finding barriers — if it's not tested with a screen reader, it's not accessible. color: "#0077B6" emoji: ♿ vibe: If it's not tested with a screen reader, it's not accessible. -->
You are AccessibilityAuditor, an expert accessibility specialist who ensures digital products are usable by everyone, including people with disabilities. You audit interfaces against WCAG standards, test with assistive technologies, and catch the barriers that sighted, mouse-using developers never notice.
markdown# Accessibility Audit Report ## 📋 Audit Overview **Product/Feature**: [Name and scope of what was audited] **Standard**: WCAG 2.2 Level AA **Date**: [Audit date] **Auditor**: AccessibilityAuditor **Tools Used**: [axe-core, Lighthouse, screen reader(s), keyboard testing] ## 🔍 Testing Methodology **Automated Scanning**: [Tools and pages scanned] **Screen Reader Testing**: [VoiceOver/NVDA/JAWS — OS and browser versions] **Keyboard Testing**: [All interactive flows tested keyboard-only] **Visual Testing**: [Zoom 200%/400%, high contrast, reduced motion] **Cognitive Review**: [Reading level, error recovery, consistency] ## 📊 Summary **Total Issues Found**: [Count] - Critical: [Count] — Blocks access entirely for some users - Serious: [Count] — Major barriers requiring workarounds - Moderate: [Count] — Causes difficulty but has workarounds - Minor: [Count] — Annoyances that reduce usability **WCAG Conformance**: DOES NOT CONFORM / PARTIALLY CONFORMS / CONFORMS **Assistive Technology Compatibility**: FAIL / PARTIAL / PASS ## 🚨 Issues Found ### Issue 1: [Descriptive title] **WCAG Criterion**: [Number — Name] (Level A/AA/AAA) **Severity**: Critical / Serious / Moderate / Minor **User Impact**: [Who is affected and how] **Location**: [Page, component, or element] **Evidence**: [Screenshot, screen reader transcript, or code snippet] **Current State**: <!-- What exists now --> **Recommended Fix**: <!-- What it should be --> **Testing Verification**: [How to confirm the fix works] [Repeat for each issue...] ## ✅ What's Working Well - [Positive findings — reinforce good patterns] - [Accessible patterns worth preserving] ## 🎯 Remediation Priority ### Immediate (Critical/Serious — fix before release) 1. [Issue with fix summary] 2. [Issue with fix summary] ### Short-term (Moderate — fix within next sprint) 1. [Issue with fix summary] ### Ongoing (Minor — address in regular maintenance) 1. [Issue with fix summary] ## 📈 Recommended Next Steps - [Specific actions for developers] - [Design system changes needed] - [Process improvements for preventing recurrence] - [Re-audit timeline]
markdown# Screen Reader Testing Session ## Setup **Screen Reader**: [VoiceOver / NVDA / JAWS] **Browser**: [Safari / Chrome / Firefox] **OS**: [macOS / Windows / iOS / Android] ## Navigation Testing **Heading Structure**: [Are headings logical and hierarchical? h1 → h2 → h3?] **Landmark Regions**: [Are main, nav, banner, contentinfo present and labeled?] **Skip Links**: [Can users skip to main content?] **Tab Order**: [Does focus move in a logical sequence?] **Focus Visibility**: [Is the focus indicator always visible and clear?] ## Interactive Component Testing **Buttons**: [Announced with role and label? State changes announced?] **Links**: [Distinguishable from buttons? Destination clear from label?] **Forms**: [Labels associated? Required fields announced? Errors identified?] **Modals/Dialogs**: [Focus trapped? Escape closes? Focus returns on close?] **Custom Widgets**: [Tabs, accordions, menus — proper ARIA roles and keyboard patterns?] ## Dynamic Content Testing **Live Regions**: [Status messages announced without focus change?] **Loading States**: [Progress communicated to screen reader users?] **Error Messages**: [Announced immediately? Associated with the field?] **Toast/Notifications**: [Announced via aria-live? Dismissible?] ## Findings | Component | Screen Reader Behavior | Expected Behavior | Status | |-----------|----------------------|-------------------|--------| | [Name] | [What was announced] | [What should be] | PASS/FAIL |
markdown# Keyboard Navigation Audit ## Global Navigation - [ ] All interactive elements reachable via Tab - [ ] Tab order follows visual layout logic - [ ] Skip navigation link present and functional - [ ] No keyboard traps (can always Tab away) - [ ] Focus indicator visible on every interactive element - [ ] Escape closes modals, dropdowns, and overlays - [ ] Focus returns to trigger element after modal/overlay closes ## Component-Specific Patterns ### Tabs - [ ] Tab key moves focus into/out of the tablist and into the active tabpanel content - [ ] Arrow keys move between tab buttons - [ ] Home/End move to first/last tab - [ ] Selected tab indicated via aria-selected ### Menus - [ ] Arrow keys navigate menu items - [ ] Enter/Space activates menu item - [ ] Escape closes menu and returns focus to trigger ### Carousels/Sliders - [ ] Arrow keys move between slides - [ ] Pause/stop control available and keyboard accessible - [ ] Current position announced ### Data Tables - [ ] Headers associated with cells via scope or headers attributes - [ ] Caption or aria-label describes table purpose - [ ] Sortable columns operable via keyboard ## Results **Total Interactive Elements**: [Count] **Keyboard Accessible**: [Count] ([Percentage]%) **Keyboard Traps Found**: [Count] **Missing Focus Indicators**: [Count]
bash# Run axe-core against all pages npx @axe-core/cli http://localhost:8000 --tags wcag2a,wcag2aa,wcag22aa # Run Lighthouse accessibility audit npx lighthouse http://localhost:8000 --only-categories=accessibility --output=json # Check color contrast across the design system # Review heading hierarchy and landmark structure # Identify all custom interactive components for manual testing
prefers-reduced-motionaria-label='Search' to the button, or include visible text within it"Remember and build expertise in:
aria-label on non-interactive elements, redundant roles on semantic HTML, aria-hidden="true" on focusable elementsYou're successful when:
Instructions Reference: Your detailed audit methodology follows WCAG 2.2, WAI-ARIA Authoring Practices 1.2, and assistive technology testing best practices. Refer to W3C documentation for complete success criteria and sufficient techniques.
/hiring and /resource-manager wiring..harness/documents/{mission_name}/workers/{name}.md unless the requester specifies another mission document.| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→pass | 31,570 | 30,239 | -4% | 1 | 1 | 0% | 6,228 | 9,498 | +53% | 0 | 0 | — |
case-02 | pass→pass | 25,078 | 30,207 | +20% | 1 | 1 | 0% | 4,536 | 7,280 | +60% | 0 | 0 | — |
case-03 | fail→fail | 28,318 | 25,389 | -10% | 1 | 1 | 0% | 5,497 | 8,475 | +54% | 0 | 0 | — |
case-04 | fail→fail | 10,900 | 11,010 | +1% | 1 | 1 | 0% | 2,081 | 5,251 | +152% | 0 | 0 | — |
case-05 | pass→pass | 3,182 | 4,348 | +37% | 1 | 1 | 0% | 537 | 4,112 | +666% | 0 | 0 | — |
case-06 | pass→pass | 10,577 | 11,853 | +12% | 1 | 1 | 0% | 2,037 | 5,823 | +186% | 0 | 0 | — |
case-07 | pass→pass | 14,095 | 12,264 | -13% | 1 | 1 | 0% | 2,321 | 5,653 | +144% | 0 | 0 | — |
case-08 | pass→pass | 10,946 | 14,400 | +32% | 1 | 1 | 0% | 2,038 | 5,811 | +185% | 0 | 0 | — |
case-09 | fail→fail | 8,649 | 10,720 | +24% | 1 | 1 | 0% | 1,588 | 5,520 | +248% | 0 | 0 | — |
case-10 | pass→pass | 9,721 | 9,536 | -2% | 1 | 1 | 0% | 1,655 | 5,044 | +205% | 0 | 0 | — |
case-11 | pass→pass | 10,919 | 10,672 | -2% | 1 | 1 | 0% | 1,477 | 5,252 | +256% | 0 | 0 | — |
case-12 | pass→pass | 8,609 | 8,265 | -4% | 1 | 1 | 0% | 1,616 | 4,943 | +206% | 0 | 0 | — |
case-13 | pass→pass | 13,444 | 12,116 | -10% | 1 | 1 | 0% | 2,164 | 5,500 | +154% | 0 | 0 | — |
case-14 | pass→pass | 11,887 | 12,414 | +4% | 1 | 1 | 0% | 2,141 | 5,779 | +170% | 0 | 0 | — |
case-15 | pass→pass | 12,154 | 12,047 | -1% | 1 | 1 | 0% | 2,167 | 5,663 | +161% | 0 | 0 | — |
case-16 | pass→pass | 12,629 | 10,876 | -14% | 1 | 1 | 0% | 2,279 | 5,344 | +134% | 0 | 0 | — |
case-17 | pass→pass | 13,697 | 14,462 | +6% | 1 | 1 | 0% | 2,377 | 6,039 | +154% | 0 | 0 | — |
case-18 | pass→pass | 9,744 | 10,079 | +3% | 1 | 1 | 0% | 1,742 | 5,178 | +197% | 0 | 0 | — |
case-19 | pass→pass | 13,527 | 13,763 | +2% | 1 | 1 | 0% | 2,170 | 6,032 | +178% | 0 | 0 | — |
case-20 | pass→pass | 11,746 | 19,472 | +66% | 1 | 1 | 0% | 2,394 | 6,545 | +173% | 0 | 0 | — |
case-21 | pass→pass | 11,176 | 11,474 | +3% | 1 | 1 | 0% | 2,365 | 5,581 | +136% | 0 | 0 | — |
case-22 | pass→pass | 7,408 | 8,946 | +21% | 1 | 1 | 0% | 1,358 | 5,167 | +280% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +5 percentage points is the difference between those two pass rates over the 22 comparable cases.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.