Accessibility Audit
Run a thorough accessibility audit and produce a remediation plan. Stack-agnostic. Anchored to WCAG 2.1 AA, with notes on AAA where relevant.
This skill goes deeper than the accessibility checks in qa-testing and design-standards. Use this when accessibility itself is the goal.
When to use
- Pre-launch accessibility verification
- Compliance preparation (ADA, EN 301 549, AODA, Section 508)
- Remediation after an audit finding or complaint
- Annual or quarterly accessibility health check
- Onboarding accessibility into a team that hasn't prioritized it before
When NOT to use
- General QA after deploys (use
qa-testing)
- Component-level accessibility implementation (use
frontend-component-build)
- Color contrast for design tokens (use
design-standards or brand-identity)
Required inputs
- The site or product under audit
- The scope (full site, specific section, specific user flow)
- The target standard (WCAG 2.1 AA is most common)
- Any specific concerns or known issues
- Tools available (automated scanners, screen readers, manual testing)
The framework: WCAG's 4 principles
WCAG organizes accessibility around four principles. The audit covers each in depth.
1. Perceivable
Information and UI must be presentable in ways users can perceive.
Audit checks:
- Text alternatives. All non-decorative images have descriptive
alt text. Decorative images use alt="". Complex images (charts, infographics) have long descriptions.
- Time-based media. Videos have captions. Pre-recorded audio has transcripts. Live audio has live captions where required.
- Adaptable. Content structure is conveyed through markup (semantic HTML), not just visual styling. Reading order makes sense when CSS is disabled.
- Distinguishable. Color is not the sole means of conveying information. Text contrast meets AA (4.5:1 normal, 3:1 large). UI element contrast meets 3:1. Audio can be paused, stopped, or muted.
2. Operable
UI components and navigation must be operable.
Audit checks:
- Keyboard accessible. All functionality available via keyboard alone. No keyboard traps. Focus visible.
- Enough time. Time limits can be adjusted, paused, or extended. Auto-updating content can be paused.
- Seizures and physical reactions. No content that flashes more than 3 times per second.
- Navigable. Skip links present. Pages have descriptive titles. Focus order is logical. Link purpose clear from text or context. Multiple ways to find pages (sitemap, search, navigation). Headings and labels are descriptive.
- Input modalities. Pointer gestures have keyboard alternatives. Pointer cancellation supported (mouse-up, not mouse-down for activation). Labels match accessible names. Motion-triggered functionality has alternatives.
3. Understandable
Information and operation must be understandable.
Audit checks:
- Readable. Page language declared (
<html lang="...">). Unusual words and abbreviations have definitions or expansions. Reading level appropriate to audience.
- Predictable. Focus does not change context unexpectedly. Input does not change context unexpectedly. Navigation is consistent across pages. Components that look similar behave similarly.
- Input assistance. Errors are identified clearly. Labels and instructions are provided for input. Error suggestions are given where possible. For pages handling legal commitments or financial transactions, errors can be reviewed and corrected before submission.
4. Robust
Content must be robust enough to work with current and future user agents.
Audit checks:
- Compatible. Markup is valid. Name, role, and value of UI components are programmatically determinable. Status messages can be programmatically determined and announced.
Audit methodology
Stage 1: Automated scan
Run automated scanners across the priority pages. These catch 30 to 50 percent of issues but miss the rest.
Tools:
- axe DevTools (browser extension)
- Lighthouse (Chrome DevTools accessibility audit)
- WAVE (browser extension)
- Pa11y (CLI for batch scanning)
Output: A list of automated findings, by page.
Stage 2: Manual keyboard testing
Unplug the mouse. Navigate the priority user flows using only keyboard.
Test:
- Tab and Shift+Tab move through interactive elements in logical order
- Enter activates buttons and links
- Space activates buttons (and toggles checkboxes)
- Arrow keys navigate within composite widgets (tabs, menus, listboxes)
- Escape dismisses modals, popovers, menus
- Focus is always visible
- Focus returns to a sensible place after modals or popovers close
- No keyboard trap (focus can always leave)
Document: Any flow where keyboard navigation breaks down.
Stage 3: Screen reader testing
Test with at least one real screen reader, or state the gap per the data-availability rule. Each combination has quirks.
Common combinations:
- VoiceOver + Safari (macOS / iOS)
- NVDA + Firefox or Chrome (Windows)
- JAWS + Chrome (Windows; commercial but common in enterprise)
- TalkBack + Chrome (Android)
Test:
- Page structure announced correctly (headings, landmarks)
- Form labels read with their inputs
- Errors announced when they appear
- Status changes announced (loading, success, error)
- Modal context announced when opened
- Images have meaningful alt text (or are correctly identified as decorative)
Stage 4: Visual testing
Verify the visual aspects of accessibility.
Test:
- Color contrast for all text/background pairs (use a contrast checker)
- UI element contrast (3:1 for icons, borders, focus rings)
- Color-blindness simulation (deuteranopia at minimum)
- Zoom to 200% - content remains usable, no horizontal scroll
- Reflow at 320px viewport
- Text spacing applied (line height, letter spacing) - no content cut off
- Motion can be reduced (
prefers-reduced-motion honored)
Stage 5: Cognitive accessibility
Often overlooked. Critical for inclusive products.
Test:
- Reading level appropriate
- Instructions clear
- Error messages explain how to fix the error, not just that one occurred
- Forms allow correction before submission
- Time limits avoidable or extendable
- Important content not dependent on memory of prior pages
Workflow
- Define scope. Full site? Specific flows? Specific page templates?
- Run automated scans. Document findings per page.
- Manual keyboard pass. Test all priority flows.
- Screen reader pass. Test with at least one combination.
- Visual checks. Contrast, zoom, color blindness, motion.
- Cognitive checks. Reading level, error handling, time limits.
- Score against WCAG. Per success criterion (level A, AA, AAA).
- Prioritize findings. Critical (blocks users), Important (degrades experience), Minor (polish).
- Write the report. Use the template in
references/audit-report-template.md.
- Build a remediation plan. Sequenced fixes with effort and impact estimates.
Severity classification
For prioritization:
Critical (P0):
- Blocks an entire user flow for an assistive-tech user
- Renders a key page completely inaccessible
- Examples: form with no labels, modal without focus management, primary CTA not keyboard-accessible
Important (P1):
- Significantly degrades the experience for assistive-tech users
- Examples: missing alt text on key images, low-contrast body text, error messages that don't announce
Minor (P2):
- Affects edge cases or specific assistive technology combinations
- Examples: minor focus order issues, missing decorative alt attributes, edge case keyboard handling
Polish (P3):
- Above-AA improvements that benefit accessibility but aren't compliance-blocking
- Examples: AAA contrast targets, additional reduced-motion variants, language attributes on inline foreign words
Failure patterns
- Automated scan only. Catches 30 to 50 percent of issues. The remaining 50 to 70 percent are in keyboard, screen reader, and cognitive testing.
- Testing only on the home page. The home page is usually the most accessible. Bugs hide in deeper flows.
- Treating accessibility as a one-time project. Accessibility erodes with every deploy. Bake it into the development cycle.
- Fixing without root cause. Patching individual issues without understanding why they happened means new ones keep appearing.
- Ignoring screen reader testing. Hard to do well, easy to skip. Single biggest source of "we thought we were accessible" surprises.
- Confusing AA and AAA. AAA is rarely the right target. AA is the practical baseline for most products.
- Treating accessibility as a designer or developer responsibility alone. Content, product, QA, and leadership all need to participate.
- Assuming compliance equals accessibility. WCAG conformance is a floor, not a ceiling. Real users may still struggle.
Output format
Default output is a comprehensive audit report at accessibility-audit.md.
Structure:
- Executive summary
- Methodology (tools used, pages tested, screen readers used)
- Findings by WCAG principle
- Critical findings (P0) with specific URLs and fixes
- Important findings (P1)
- Minor findings (P2)
- Polish (P3)
- Remediation roadmap (sequenced and prioritized)
- Appendices (full automated scan results, keyboard navigation notes, screen reader notes)
Plus a remediation tracking spreadsheet with one row per finding.
If required data is unavailable
This skill's output depends on data, measurements, or tool results it cannot generate on its own. When a required input, tool, or data source is unavailable or unverifiable, the sanctioned output is the deliverable with the gap stated: what was needed, what was actually obtained or verified, and which parts of the output are affected. Fabricating, estimating, or interpolating a required number to complete the deliverable is never sanctioned. A stated gap is a complete answer.
Reference files
references/audit-report-template.md - Full audit report template.references/wcag-quick-reference.md - Condensed WCAG 2.1 AA criteria with audit checks.references/aria-patterns.md - Decision-grade ARIA patterns. Semantic-HTML-first principle, common interactive widgets (accordion, tabs, modal, toggle, disclosure, navigation), live regions, hiding patterns, labeling, state indicators, anti-patterns.
1---2name: accessibility-audit3description: Run a comprehensive WCAG accessibility audit covering perceivable, operable, understandable, and robust principles. Use this skill whenever the user wants to audit accessibility, review WCAG compliance, fix accessibility issues, prepare for accessibility certification, address an accessibility lawsuit risk, or systematically improve a site's accessibility. Triggers on accessibility audit, WCAG audit, a11y audit, accessibility compliance, ADA compliance, screen reader test, keyboard navigation, accessibility report, fix accessibility, axe scan. Also triggers when accessibility issues have been reported and need systematic remediation.4---56# Accessibility Audit78Run a thorough accessibility audit and produce a remediation plan. Stack-agnostic. Anchored to WCAG 2.1 AA, with notes on AAA where relevant.910This skill goes deeper than the accessibility checks in `qa-testing` and `design-standards`. Use this when accessibility itself is the goal.1112---1314## When to use1516- Pre-launch accessibility verification17- Compliance preparation (ADA, EN 301 549, AODA, Section 508)18- Remediation after an audit finding or complaint19- Annual or quarterly accessibility health check20- Onboarding accessibility into a team that hasn't prioritized it before2122## When NOT to use2324- General QA after deploys (use `qa-testing`)25- Component-level accessibility implementation (use `frontend-component-build`)26- Color contrast for design tokens (use `design-standards` or `brand-identity`)2728---2930## Required inputs3132- The site or product under audit33- The scope (full site, specific section, specific user flow)34- The target standard (WCAG 2.1 AA is most common)35- Any specific concerns or known issues36- Tools available (automated scanners, screen readers, manual testing)3738---3940## The framework: WCAG's 4 principles4142WCAG organizes accessibility around four principles. The audit covers each in depth.4344### 1. Perceivable4546Information and UI must be presentable in ways users can perceive.4748**Audit checks:**4950- **Text alternatives.** All non-decorative images have descriptive `alt` text. Decorative images use `alt=""`. Complex images (charts, infographics) have long descriptions.51- **Time-based media.** Videos have captions. Pre-recorded audio has transcripts. Live audio has live captions where required.52- **Adaptable.** Content structure is conveyed through markup (semantic HTML), not just visual styling. Reading order makes sense when CSS is disabled.53- **Distinguishable.** Color is not the sole means of conveying information. Text contrast meets AA (4.5:1 normal, 3:1 large). UI element contrast meets 3:1. Audio can be paused, stopped, or muted.5455### 2. Operable5657UI components and navigation must be operable.5859**Audit checks:**6061- **Keyboard accessible.** All functionality available via keyboard alone. No keyboard traps. Focus visible.62- **Enough time.** Time limits can be adjusted, paused, or extended. Auto-updating content can be paused.63- **Seizures and physical reactions.** No content that flashes more than 3 times per second.64- **Navigable.** Skip links present. Pages have descriptive titles. Focus order is logical. Link purpose clear from text or context. Multiple ways to find pages (sitemap, search, navigation). Headings and labels are descriptive.65- **Input modalities.** Pointer gestures have keyboard alternatives. Pointer cancellation supported (mouse-up, not mouse-down for activation). Labels match accessible names. Motion-triggered functionality has alternatives.6667### 3. Understandable6869Information and operation must be understandable.7071**Audit checks:**7273- **Readable.** Page language declared (`<html lang="...">`). Unusual words and abbreviations have definitions or expansions. Reading level appropriate to audience.74- **Predictable.** Focus does not change context unexpectedly. Input does not change context unexpectedly. Navigation is consistent across pages. Components that look similar behave similarly.75- **Input assistance.** Errors are identified clearly. Labels and instructions are provided for input. Error suggestions are given where possible. For pages handling legal commitments or financial transactions, errors can be reviewed and corrected before submission.7677### 4. Robust7879Content must be robust enough to work with current and future user agents.8081**Audit checks:**8283- **Compatible.** Markup is valid. Name, role, and value of UI components are programmatically determinable. Status messages can be programmatically determined and announced.8485---8687## Audit methodology8889### Stage 1: Automated scan9091Run automated scanners across the priority pages. These catch 30 to 50 percent of issues but miss the rest.9293**Tools:**94- axe DevTools (browser extension)95- Lighthouse (Chrome DevTools accessibility audit)96- WAVE (browser extension)97- Pa11y (CLI for batch scanning)9899**Output:** A list of automated findings, by page.100101### Stage 2: Manual keyboard testing102103Unplug the mouse. Navigate the priority user flows using only keyboard.104105**Test:**106- Tab and Shift+Tab move through interactive elements in logical order107- Enter activates buttons and links108- Space activates buttons (and toggles checkboxes)109- Arrow keys navigate within composite widgets (tabs, menus, listboxes)110- Escape dismisses modals, popovers, menus111- Focus is always visible112- Focus returns to a sensible place after modals or popovers close113- No keyboard trap (focus can always leave)114115**Document:** Any flow where keyboard navigation breaks down.116117### Stage 3: Screen reader testing118119Test with at least one real screen reader, or state the gap per the data-availability rule. Each combination has quirks.120121**Common combinations:**122- VoiceOver + Safari (macOS / iOS)123- NVDA + Firefox or Chrome (Windows)124- JAWS + Chrome (Windows; commercial but common in enterprise)125- TalkBack + Chrome (Android)126127**Test:**128- Page structure announced correctly (headings, landmarks)129- Form labels read with their inputs130- Errors announced when they appear131- Status changes announced (loading, success, error)132- Modal context announced when opened133- Images have meaningful alt text (or are correctly identified as decorative)134135### Stage 4: Visual testing136137Verify the visual aspects of accessibility.138139**Test:**140- Color contrast for all text/background pairs (use a contrast checker)141- UI element contrast (3:1 for icons, borders, focus rings)142- Color-blindness simulation (deuteranopia at minimum)143- Zoom to 200% - content remains usable, no horizontal scroll144- Reflow at 320px viewport145- Text spacing applied (line height, letter spacing) - no content cut off146- Motion can be reduced (`prefers-reduced-motion` honored)147148### Stage 5: Cognitive accessibility149150Often overlooked. Critical for inclusive products.151152**Test:**153- Reading level appropriate154- Instructions clear155- Error messages explain how to fix the error, not just that one occurred156- Forms allow correction before submission157- Time limits avoidable or extendable158- Important content not dependent on memory of prior pages159160---161162## Workflow1631641. **Define scope.** Full site? Specific flows? Specific page templates?1652. **Run automated scans.** Document findings per page.1663. **Manual keyboard pass.** Test all priority flows.1674. **Screen reader pass.** Test with at least one combination.1685. **Visual checks.** Contrast, zoom, color blindness, motion.1696. **Cognitive checks.** Reading level, error handling, time limits.1707. **Score against WCAG.** Per success criterion (level A, AA, AAA).1718. **Prioritize findings.** Critical (blocks users), Important (degrades experience), Minor (polish).1729. **Write the report.** Use the template in [`references/audit-report-template.md`](references/audit-report-template.md).17310. **Build a remediation plan.** Sequenced fixes with effort and impact estimates.174175---176177## Severity classification178179For prioritization:180181**Critical (P0):**182- Blocks an entire user flow for an assistive-tech user183- Renders a key page completely inaccessible184- Examples: form with no labels, modal without focus management, primary CTA not keyboard-accessible185186**Important (P1):**187- Significantly degrades the experience for assistive-tech users188- Examples: missing alt text on key images, low-contrast body text, error messages that don't announce189190**Minor (P2):**191- Affects edge cases or specific assistive technology combinations192- Examples: minor focus order issues, missing decorative alt attributes, edge case keyboard handling193194**Polish (P3):**195- Above-AA improvements that benefit accessibility but aren't compliance-blocking196- Examples: AAA contrast targets, additional reduced-motion variants, language attributes on inline foreign words197198---199200## Failure patterns201202- **Automated scan only.** Catches 30 to 50 percent of issues. The remaining 50 to 70 percent are in keyboard, screen reader, and cognitive testing.203- **Testing only on the home page.** The home page is usually the most accessible. Bugs hide in deeper flows.204- **Treating accessibility as a one-time project.** Accessibility erodes with every deploy. Bake it into the development cycle.205- **Fixing without root cause.** Patching individual issues without understanding why they happened means new ones keep appearing.206- **Ignoring screen reader testing.** Hard to do well, easy to skip. Single biggest source of "we thought we were accessible" surprises.207- **Confusing AA and AAA.** AAA is rarely the right target. AA is the practical baseline for most products.208- **Treating accessibility as a designer or developer responsibility alone.** Content, product, QA, and leadership all need to participate.209- **Assuming compliance equals accessibility.** WCAG conformance is a floor, not a ceiling. Real users may still struggle.210211---212213## Output format214215Default output is a comprehensive audit report at `accessibility-audit.md`.216217Structure:2181. Executive summary2192. Methodology (tools used, pages tested, screen readers used)2203. Findings by WCAG principle2214. Critical findings (P0) with specific URLs and fixes2225. Important findings (P1)2236. Minor findings (P2)2247. Polish (P3)2258. Remediation roadmap (sequenced and prioritized)2269. Appendices (full automated scan results, keyboard navigation notes, screen reader notes)227228Plus a remediation tracking spreadsheet with one row per finding.229230---231232## If required data is unavailable233234This skill's output depends on data, measurements, or tool results it cannot generate on its own. When a required input, tool, or data source is unavailable or unverifiable, the sanctioned output is the deliverable with the gap stated: what was needed, what was actually obtained or verified, and which parts of the output are affected. Fabricating, estimating, or interpolating a required number to complete the deliverable is never sanctioned. A stated gap is a complete answer.235236---237238## Reference files239240- [`references/audit-report-template.md`](references/audit-report-template.md) - Full audit report template.241- [`references/wcag-quick-reference.md`](references/wcag-quick-reference.md) - Condensed WCAG 2.1 AA criteria with audit checks.242- [`references/aria-patterns.md`](references/aria-patterns.md) - Decision-grade ARIA patterns. Semantic-HTML-first principle, common interactive widgets (accordion, tabs, modal, toggle, disclosure, navigation), live regions, hiding patterns, labeling, state indicators, anti-patterns.
rampstackco