accessibility-auditing

Audit web pages for accessibility issues using browser snapshots and keyboard navigation checks.

672|104|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill accessibility-auditing-spencerpauly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-auditing
Source: https://github.com/spencerpauly/awesome-cursor-skills/tree/main/resources/accessibility-auditing
Command: npx skills add https://github.com/spencerpauly/awesome-cursor-skills --skill accessibility-auditing-spencerpauly

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly inspect a web page for accessibility problems that are easy to miss during development, such as unlabeled controls, weak keyboard support, and broken ARIA usage.

Core Features & Use Cases

  • Accessibility Tree Review: Inspect the browser's accessibility snapshot to catch missing labels, incorrect semantics, and focusable elements that screen readers will struggle with.
  • Keyboard Navigation Checks: Verify tab order, visible focus, and escape behavior for dialogs, menus, and other interactive UI patterns.
  • Visual Contrast Spot-Checks: Use screenshots to identify text or control states that are too faint to read clearly.
  • Use Case: After shipping a new header, form, or modal, use this Skill to audit the page and turn accessibility findings into concrete code fixes before release.

Quick Start

Ask Cursor to audit the current page for accessibility issues using the browser snapshot and keyboard navigation checks.

Frequently Asked Questions about accessibility-auditing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a web page for accessibility issues using a browser snapshot?

To audit web page accessibility, inspect the browser's accessibility snapshot to review the accessibility tree for missing labels, incorrect semantics, and problematic focusable elements that screen readers struggle with.

How do I verify keyboard navigation and tab order for interactive UI patterns?

Verify keyboard navigation by checking tab order, visible focus, and escape behavior for dialogs and menus to ensure interactive UI patterns meet keyboard and screen-reader expectations.

How do I check ARIA patterns and semantic structure for screen reader compatibility?

Check ARIA patterns and semantic structure by verifying accessible names, landmarks, and focus management against screen-reader expectations to ensure controls are properly labeled and navigable.

Can I use this to run accessibility regression checks after frontend changes?

Yes, you can run accessibility regression checks after frontend changes by auditing new headers, forms, or modals to validate labels, landmarks, and focus order before release.

How do I spot visual contrast issues in text and control states?

Spot visual contrast issues by using screenshots to identify text or control states that are too faint to read clearly, ensuring UI elements meet visual accessibility standards.

What is the best way to find unlabeled controls and broken ARIA usage during development?

The best way to find unlabeled controls and broken ARIA usage is to inspect the browser's accessibility snapshot, which reveals missing labels and incorrect semantics that are easy to miss during development.