skills.rest
esneiderbravo
esneiderbravoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

accessibility-standards

Audit UI accessibility for WCAG 2.2 AA compliance with automated and manual checks.

1|Updated Apr 17, 2026
Search Tags:#accessibility#a11y#wcag#keyboard#semantic-html#aria
One-click install
npx skills add https://github.com/esneiderbravo/hackaton --skill accessibility-standards-esneiderbravo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-standards
Source: https://github.com/esneiderbravo/hackaton/tree/main/.github/skills/accessibility-standards
Command: npx skills add https://github.com/esneiderbravo/hackaton --skill accessibility-standards-esneiderbravo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured workflow to audit and remediate UI accessibility, driving WCAG 2.2 AA compliance across web applications and components.

Core Features & Use Cases

  • Automated and manual checks for semantic HTML, ARIA usage, keyboard navigation, and screen-reader compatibility.
  • Guided remediation workflow that prioritizes critical issues (P0) to non-critical improvements (P2) and documents results for handoff.
  • Reusable playbooks for audits during development, code reviews, and UI refactoring to maintain accessibility across components and pages.

Quick Start

Run an accessibility audit and implement semantic HTML, ARIA, keyboard, and screen-reader checks to ensure WCAG 2.2 AA compliance.

Frequently Asked Questions about accessibility-standards

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

FAQPage Schema
How do I audit my web UI for WCAG 2.2 AA compliance?▼

Audit web UI for WCAG 2.2 AA compliance by running automated checks alongside manual reviews of semantic HTML, ARIA usage, keyboard navigation, and screen-reader compatibility to produce an actionable remediation report.

What is the best way to fix semantic HTML and ARIA issues during a code review?▼

Fix semantic HTML and ARIA issues during code review by applying a structured accessibility workflow that prioritizes critical problems from P0 to P2 and documents remediation steps for handoff.

How do I test keyboard navigation and screen-reader compatibility for web components?▼

Test keyboard navigation and screen-reader compatibility by validating focus management, semantic roles, and ARIA attributes across pages and components to ensure full WCAG 2.2 AA compliance.

Can I use this accessibility workflow for UI refactoring and component updates?▼

You can use this accessibility workflow for UI refactoring and component updates by applying reusable playbooks that maintain WCAG 2.2 AA standards across continuous development cycles.

Why does my web application fail screen-reader validation despite having ARIA attributes?▼

Screen-reader validation often fails when ARIA attributes are misused or lack proper semantic HTML backing, requiring a structured audit to correct roles, states, and keyboard interactions.

Do I need automated checks or manual reviews to ensure WCAG 2.2 AA accessibility?▼

Ensuring WCAG 2.2 AA accessibility requires both automated checks for baseline errors and manual reviews for semantic HTML, ARIA logic, keyboard navigation, and screen-reader compatibility.

Related Skills

Explore More Design & Creative Skills→
yashraj22yashraj22

web-design-guidelines

Identify UI accessibility and design issues in HTML, CSS, and JavaScript files.

Community
Intermediate
RB-chrismandichRB-chrismandich
1

a11y-audit

Audit web projects for WCAG 2.2 AA accessibility issues with ARIA and semantic HTML checks.

Community
Advanced
kennedym-dskennedym-ds
14

accessibility-wcag

Evaluate and implement WCAG 2.1 AA accessibility patterns for frontend web development.

Community
Advanced
wredziowredzio

accessibility

Identify and remediate WCAG 2.1 AA accessibility issues in web pages.

Community
Advanced