accessibility-auditing

Audit web page accessibility by analyzing Cursor's ARIA tree snapshots.

2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill accessibility-auditing-kscius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-auditing
Source: https://github.com/kscius/KS-Cursor-Orchestrator/tree/main/skills/accessibility-auditing
Command: npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill accessibility-auditing-kscius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits web pages for accessibility issues by analyzing Cursor's ARIA snapshots to identify missing labels, poor keyboard navigation, contrast problems, and ARIA misuse.

Core Features & Use Cases

  • Capture and inspect the accessibility tree to detect common issues.
  • Validate keyboard navigability, landmark presence, and ARIA semantics across pages.
  • Use in QA, design reviews, and before-launch accessibility checks to ensure inclusive experiences.

Quick Start

Open a target URL in Cursor, run a browser snapshot, review the detected issues, and begin remediation.

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 ARIA snapshots?

Audit web page accessibility by loading a target URL in Cursor, generating a browser snapshot, and analyzing the ARIA tree to detect missing labels, poor keyboard navigation, contrast problems, and ARIA misuse for remediation.

What common accessibility issues can be detected from an ARIA tree snapshot?

An ARIA tree snapshot detects missing labels, poor keyboard navigation, incorrect ARIA semantics, improper landmark usage, and color contrast problems to ensure inclusive web experiences.

How do I test keyboard navigation and focus order for accessibility conformance?

Test keyboard navigation by using browser press commands on a loaded web page snapshot to validate tab sequence, verify landmark presence, and ensure ARIA semantics meet accessibility conformance.

Can I use this for QA accessibility regression checks before launch?

Yes, you can run on-page accessibility audits for QA regression checks and before-launch reviews across internal and customer-facing pages to validate keyboard navigability and ARIA correctness.

What's the best way to check for missing labels and landmark usage on a web page?

The best way to check for missing labels and landmark usage is to capture an accessibility tree snapshot of the target URL and inspect the ARIA semantics for inclusive design compliance.