accessibility-auditor

Name: accessibility-auditor
Availability: InStock
Author: gwpjp

Audit running web applications for accessibility issues via the accessibility tree and keyboard navigation.

3|Updated Jan 31, 2026

Search Tags:#accessibility #a11y #ARIA #audit #keyboard-navigation #focus-management

Ready to run

npx skills add https://github.com/gwpjp/Web3-Claude --skill accessibility-auditor-gwpjp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility-auditor
Source: https://github.com/gwpjp/Web3-Claude/tree/main/.claude/skills/accessibility-auditor
Command: npx skills add https://github.com/gwpjp/Web3-Claude --skill accessibility-auditor-gwpjp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits the running app for accessibility issues by inspecting the accessibility tree, testing keyboard navigation, and verifying that interactive elements are properly labeled and focusable.

Core Features & Use Cases

ARIA labeling checks for buttons, inputs, and roles
Keyboard navigation and focus management verification
Focus visibility and semantic structure validation
Use Case: QA after UI changes to ensure new components are accessible

Quick Start

Use the accessibility-auditor skill to validate the current UI for accessibility issues. Ensure a Chrome tab is open with the app loaded and prerequisites are met.

Frequently Asked Questions about accessibility-auditor

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

FAQPage Schema

How do I audit my web application for keyboard navigation and ARIA issues?▼

To audit web application accessibility, use the accessibility-auditor to inspect the accessibility tree and test keyboard navigation. It verifies ARIA labeling, focus management, and visible focus indicators across routes to identify gaps in interactive components.

What is the best way to check focus management after adding new interactive UI components?▼

Checking focus management after UI changes requires auditing the running app's accessibility tree. This skill validates that newly added interactive components have proper ARIA labels, semantic structure, and visible focus indicators during keyboard navigation.

Do I need a running browser context to test ARIA labeling and accessibility tree structures?▼

Yes, you need a running browser context with the app loaded to test ARIA labeling and accessibility tree structures. The skill performs automated checks and provides manual keyboard navigation guidance directly within the active browser environment.

Can I validate visible focus indicators across different application routes?▼

Yes, you can validate visible focus indicators across different application routes. The skill audits newly added interactive components by inspecting the accessibility tree and verifying that focus visibility and semantic structure are maintained throughout the app.

What accessibility checks are needed for newly added interactive UI components?▼

Accessibility checks for new UI components must cover ARIA labeling, keyboard navigation, and focus management. The skill inspects the running app's accessibility tree to verify semantic structure, focus visibility, and proper interactive element labeling.

How does inspecting the accessibility tree identify keyboard navigation gaps?▼

Inspecting the accessibility tree identifies keyboard navigation gaps by validating semantic structure and focus management. The skill uses automated checks and manual keyboard navigation guidance to detect missing ARIA labels and invisible focus indicators in the running app.