
Accessibility Auditing
- 243 installs
- 655 repo stars
- Updated August 2, 2026
- spencerpauly/awesome-cursor-skills
accessibility-auditing is a Claude Code skill that audits a web page's accessibility tree for missing labels, keyboard, ARIA and contrast issues.
About
accessibility-auditing is a Claude Code skill that audits a web page for accessibility issues using the browser accessibility tree. It captures the aria snapshot, checks for missing labels, non-semantic HTML, broken keyboard navigation, ARIA misuse and contrast problems, then reports critical issues and warnings and applies source fixes. A developer uses it to catch a11y defects before shipping. It is mislabeled as security in the current catalog.
- Audits the browser aria/accessibility tree
- Missing-label, semantic-HTML and ARIA checks
- Keyboard-navigation and focus-order testing
- Reports issues then fixes source
Accessibility Auditing by the numbers
- 243 all-time installs (skills.sh)
- +35 installs in the week ending Jul 27, 2026 (Skillselion tracking)
- Ranked #766 of 2,153 Testing & QA skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
accessibility-auditing capabilities & compatibility
free, no API key required
- Capabilities
- accessibility audit · aria audit · keyboard navigation test · contrast check · semantic html check
- Use cases
- testing · ui design
- IDEs
- cursor ide
- Pricing
- Free
What accessibility-auditing says it does
Use Cursor's browser aria snapshots to audit a page for accessibility issues — missing labels, broken tab order, contrast, and ARIA misuse.
Use `browser_snapshot` — this returns the aria/accessibility tree of the page. This is the same tree that screen readers use.
npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill accessibility-auditingAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 243 |
|---|---|
| repo stars | ★ 655 |
| Last updated | August 2, 2026 |
| Repository | spencerpauly/awesome-cursor-skills ↗ |
Is this page accessible, and where are the a11y defects?
testing
Who is it for?
Front-end developers checking a page for a11y defects before release.
Skip if: Security review, or non-web UIs without an accessibility tree.
When should I use this skill?
When auditing a web page for accessibility issues - missing labels, broken tab order, contrast, and ARIA misuse.
What you get
An accessibility audit listing critical issues, warnings and passes, with source fixes applied.
By the numbers
- 6-step accessibility audit workflow
Files
Accessibility Auditing
Audit a web page for accessibility issues using Cursor's built-in browser without external tools.
Workflow
1. Open the Page
Use browser_navigate to open the target URL.
2. Capture the Accessibility Tree
Use browser_snapshot — this returns the aria/accessibility tree of the page. This is the same tree that screen readers use.
3. Audit the Tree
Check for these issues:
Missing Labels
buttonelements with no accessible name (no text, noaria-label)imgelements with noalttextinputelements with no associatedlabeloraria-labela(link) elements with no text content- Icon-only buttons missing
aria-label
Semantic HTML
- Clickable
divorspanelements → should bebuttonora - Missing
nav,main,header,footerlandmarks - Headings that skip levels (h1 → h3)
- Lists that aren't using
ul/ol/li
Keyboard Navigation
- Interactive elements missing from tab order
- Custom widgets without
roleand keyboard handlers - Focus traps in modals (should trap focus, but also allow Escape to close)
- Skip-to-content link missing
ARIA Issues
aria-hidden="true"on focusable elements- Invalid
rolevalues aria-expandedwithout corresponding collapsible contentaria-controlspointing to non-existent IDs
Contrast (use screenshot for visual check)
- Light gray text on white backgrounds
- Placeholder text that's too faint
- Disabled states that are indistinguishable
4. Test Keyboard Navigation
Use browser_press to simulate Tab key presses and verify:
- Every interactive element receives focus
- Focus order is logical (top-to-bottom, left-to-right)
- Focus is visible (focus ring or outline)
- Escape closes modals/dropdowns
5. Report
Accessibility Audit:
Critical:
- 3 buttons with no accessible name (header icons)
- Login form inputs missing labels
Warnings:
- Heading levels skip from h1 to h3
- No skip-to-content link
- 2 clickable divs should be buttons
Passed:
- All images have alt text
- Landmarks present (nav, main, footer)
- Focus order is logical6. Fix
For each issue, apply the fix in the source code. Common fixes:
- Add
aria-label="Close"to icon buttons - Wrap inputs in
<label>or addhtmlFor - Change
<div onClick>to<button> - Add
alttext to images - Fix heading hierarchy
Related skills
FAQ
What does accessibility-auditing check?
Missing labels, semantic HTML, keyboard navigation, ARIA issues and contrast, using the browser accessibility tree that screen readers use.
Does it fix the issues it finds?
Yes. After reporting, it applies common fixes in source such as adding aria-label, wrapping inputs in labels and correcting heading hierarchy.