skills.rest
jnlanahan
jnlanahanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

accessibility

Audit UI codebases for WCAG 2.1 AA violations and generate prioritized remediation plans.

Updated Apr 30, 2026
Search Tags:#accessibility#screen reader#keyboard navigation#audit#wcag#aria#ui compliance
One-click install
npx skills add https://github.com/jnlanahan/Product-Agents-and-Skills --skill accessibility-jnlanahan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/jnlanahan/Product-Agents-and-Skills/tree/main/skills/5-Validate-Accessibility
Command: npx skills add https://github.com/jnlanahan/Product-Agents-and-Skills --skill accessibility-jnlanahan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accessibility audits can be hard to run reliably, leaving keyboard, screen-reader, and WCAG compliance problems undiscovered until users are impacted.

Core Features & Use Cases

  • Automated WCAG 2.1 AA scanning to detect component-level accessibility violations using static analysis.
  • Prioritized fix planning that ranks findings by Critical/High/Medium/Low impact and estimates effort.
  • Guided, approval-based remediation that applies one fix at a time with visible before/after changes and prompts for confirmation.
  • Manual testing checklist for issues static analysis can miss, including contrast, keyboard navigation, focus indicators, screen reader behavior, motion sensitivity, and 200% zoom.

Quick Start

Run an accessibility audit for your project and generate a prioritized WCAG 2.1 AA fix plan for any files flagged by the scanner.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I run a WCAG 2.1 AA accessibility audit on my UI codebase?▼

Run an accessibility audit to scan your UI codebase for WCAG 2.1 AA violations using static analysis. The scanner detects component-level issues with keyboard navigation, screen reader support, and ARIA semantics, then outputs a prioritized list of findings.

What is the best way to prioritize and fix ARIA and keyboard navigation violations?▼

The best way to fix ARIA and keyboard navigation violations is using a prioritized remediation plan that ranks findings by Critical, High, Medium, or Low severity. Each violation includes an effort estimate and guided, approval-based fixes applied one at a time.

Does static analysis catch all WCAG compliance issues, or do I need manual testing?▼

Static analysis does not catch all WCAG compliance issues. After automated scanning, you must complete a manual testing checklist covering contrast, keyboard navigation, focus indicators, screen reader behavior, motion sensitivity, and 200% zoom.

Can I automatically apply accessibility fixes without reviewing the changes first?▼

No, you cannot automatically apply fixes without review. The remediation process is approval-based, applying one fix at a time with visible before and after changes. Explicit user confirmation is required for each fix.

When do I need to check accessible labeling and screen reader support in my components?▼

You need to check accessible labeling and screen reader support when your UI components lack correct ARIA semantics. An accessibility audit scans for these component-level violations and generates a remediation plan to ensure WCAG 2.1 AA compliance.

Related Skills

Explore More Design & Creative Skills→
slbugslbug
7

rb:secrets

Detect leaked secrets and exposed credentials in Ruby codebases.

Community
Intermediate
clawpod-appclawpod-app
46

accessibility-review

Audit designs or pages for WCAG 2.1 AA compliance with remediation guidance.

Community
Intermediate
Tristan578Tristan578
5

web-accessibility

Implement WCAG 2.1-compliant web interfaces with semantic HTML and ARIA.

Community
Advanced
logo-solutionslogo-solutions

browser-testing-with-devtools

Inspect live DOM, console, network, and performance state in Chromium-based browsers.

Official
Advanced