skills.rest
Prathmesh2000
Prathmesh2000COMMUNITY
Explore all skills by this author →
GitHub

accessibility-tester

Audit frontend UIs for WCAG 2.1 AA compliance and generate remediation reports.

1|Updated Mar 4, 2026
Search Tags:#accessibility#a11y#wcag#screen-reader#color-contrast#keyboard-navigation
One-click install
npx skills add https://github.com/Prathmesh2000/cursor_agent-orchestrator --skill accessibility-tester-prathmesh2000
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-tester
Source: https://github.com/Prathmesh2000/cursor_agent-orchestrator/tree/main/agent-system/skills/accessibility-tester
Command: npx skills add https://github.com/Prathmesh2000/cursor_agent-orchestrator --skill accessibility-tester-prathmesh2000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits and fixes UI for WCAG 2.1 AA compliance, screen reader support, keyboard navigation, and inclusive design, reducing accessibility risks and rework.

Core Features & Use Cases

  • WCAG 2.1 AA checks across perceivable, operable, understandable, and robust criteria.
  • Automated tests for keyboard navigation, focus visibility, color contrast, and ARIA labeling.
  • Generates an actionable remediation report with code examples and integration tips for CI.

Quick Start

Audit a frontend UI for WCAG 2.1 AA compliance and produce a remediation plan with concrete fixes.

Frequently Asked Questions about accessibility-tester

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

FAQPage Schema
How do I audit my frontend UI for WCAG 2.1 AA accessibility compliance?▼

To audit frontend UI for WCAG 2.1 AA accessibility compliance, run automated axe-core and Playwright tests to check keyboard navigation, ARIA labeling, and color contrast, which generates an actionable remediation report with code examples.

What is the best way to fix keyboard navigation and screen reader compatibility issues in web applications?▼

Fixing keyboard navigation and screen reader compatibility issues requires validating ARIA labeling, checking focus management, and running automated Playwright tests to identify interactive components that fail WCAG 2.1 AA operable and robust criteria.

Can I use axe-core with Playwright to check color contrast and ARIA labeling on interactive components?▼

Yes, you can use axe-core with Playwright to check color contrast and validate ARIA labeling on interactive components like dashboards and forms, ensuring your frontend UI meets WCAG 2.1 AA perceivable criteria.

How do I generate an actionable accessibility audit report with concrete remediation steps?▼

Generate an actionable accessibility audit report with remediation steps by running automated axe-core tests on your frontend UI, which produces concrete code examples and integration tips for CI based on detected ARIA and focus management issues.

Does WCAG 2.1 AA conformance testing work for complex dashboards and interactive forms?▼

WCAG 2.1 AA conformance testing works for complex dashboards and interactive forms by validating focus visibility, keyboard navigation, and screen reader compatibility across perceivable, operable, understandable, and robust criteria to reduce accessibility risks.

Related Skills

Explore More Design & Creative Skills→
V4-CompanyV4-Company
2

marsai:dev-frontend-accessibility

Run axe-core accessibility scans on React/TypeScript UI components.

Official
Intermediate
clawpod-appclawpod-app
46

accessibility-review

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

Community
Intermediate
JaivishChauhanJaivishChauhan
6

accessibility

Apply WCAG-compliant semantics to portfolio pages for keyboard and screen reader accessibility.

Community
Intermediate
HouseofmvpsHouseofmvps
115

a11y

Detect and fix deterministic WCAG 2.2 A/AA accessibility violations in HTML files.

Community
Advanced