web-accessibility

Enforce WCAG 2.1 AA accessibility requirements for web UI components.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ensure web interfaces meet WCAG 2.1 AA accessibility standards, reducing accessibility risks and improving usability for people with disabilities.

Core Features & Use Cases

  • Semantic HTML: enforce proper element usage (buttons, links, headings) and avoid relying on non-semantic divs.
  • ARIA & Labels: ensure all controls have accessible labels and appropriate ARIA attributes.
  • Keyboard Navigation: verify all controls are reachable via keyboard and focus management is correct.
  • Color Contrast: validate sufficient contrast ratios and avoid color-only indicators.
  • Audit & Review: supports UI component reviews and live browser checks; integrate with existing accessibility-auditing workflows.

Quick Start

Audit a UI component for WCAG 2.1 AA conformance and apply semantic HTML, ARIA, keyboard navigation, and contrast improvements.

Frequently Asked Questions about web-accessibility

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

FAQPage Schema
How do I check WCAG 2.1 AA compliance for web UI components?

Check WCAG 2.1 AA compliance by auditing UI components for semantic HTML, ARIA labeling, keyboard navigation, color contrast, and focus management to identify accessibility risks and ensure usability for people with disabilities.

What is the best way to enforce semantic HTML and ARIA labels for accessibility?

Enforce semantic HTML and ARIA labels by replacing non-semantic divs with proper elements like buttons and headings, ensuring all controls have accessible labels and appropriate ARIA attributes for screen reader compatibility.

How do I verify keyboard navigation and focus management in web forms and dashboards?

Verify keyboard navigation by confirming all interactive controls in dashboards and forms are reachable via keyboard, checking that focus management correctly handles transitions between UI components without trapping users.

How do I validate color contrast ratios to avoid color-only indicators?

Validate color contrast by checking that foreground and background combinations meet WCAG 2.1 AA contrast ratios, and ensure information is not conveyed through color-only indicators to support users with visual impairments.

Can I integrate WCAG 2.1 AA accessibility checks into existing component review workflows?

Integrate WCAG 2.1 AA checks into existing workflows by applying accessibility audits during UI component reviews and live browser checks, identifying structural and labeling issues before deployment to reduce accessibility risks.

Why does my web widget fail accessibility audits despite using ARIA attributes?

Widgets fail accessibility audits when ARIA attributes are applied to non-semantic elements instead of using proper semantic HTML, or when keyboard navigation and focus management are not correctly implemented for interactive controls.