accessibility

Audit web pages against WCAG 2.1 POUR and generate prioritized accessibility fixes.

1|Updated Mar 6, 2026

Search Tags:#screen reader #keyboard navigation #color contrast #web accessibility #focus management #aria #wcag 2.1

Ready to run

npx skills add https://github.com/barateza/dubweave --skill accessibility-barateza

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/barateza/dubweave/tree/main/.agent/skills/accessibility
Command: npx skills add https://github.com/barateza/dubweave --skill accessibility-barateza

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Accessibility guidance helps you remove barriers that prevent people with disabilities from using your website effectively, safely, and independently.

Core Features & Use Cases

WCAG 2.1-aligned improvements across POUR (Perceivable, Operable, Understandable, Robust), including keyboard support, focus visibility, and robust markup.
Practical fixes for common issues like missing alt text, insufficient color contrast, missing form labels, weak error handling, and non-semantic ARIA usage.
Testing and validation workflows using Lighthouse accessibility checks, axe, and manual screen reader/keyboard test checklists.

Quick Start

Use the accessibility skill to perform a WCAG 2.1-focused audit of your page and generate prioritized fixes for the highest-impact issues you discover.

Frequently Asked Questions about accessibility

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

FAQPage Schema

How do I audit my web page for WCAG 2.1 accessibility compliance?▼

To audit web accessibility for WCAG 2.1 compliance, evaluate your UI against the POUR principles to detect barriers in keyboard operability, perceivable alternatives, semantic HTML, and ARIA roles. Generate prioritized fixes for issues like missing alt text, insufficient color contrast, and weak form error handling.

How do I fix keyboard navigation and focus management issues on my website?▼

Fix keyboard navigation and focus management by checking keyboard operability and ensuring focus visibility across interactive elements. Correct UI barriers by implementing robust semantic HTML and ARIA patterns to maintain logical focus order and provide clear status updates via live regions.

What's the best way to test screen reader compatibility and ARIA usage?▼

Testing screen reader compatibility and ARIA usage involves validating robust semantic markup and checking live-region patterns for status updates. Use manual screen reader test checklists alongside automated tools like Lighthouse and axe to detect non-semantic ARIA and verify perceivable alternatives.

How do I correct missing form labels and insufficient color contrast for web accessibility?▼

Correct missing form labels and insufficient color contrast by applying WCAG 2.1 POUR guidelines to ensure content is perceivable and understandable. Implement proper form labeling, clear error messaging, and adjust color contrast ratios to remove barriers that prevent independent usage.

Can I use Lighthouse and axe to validate WCAG 2.1 POUR requirements?▼

Yes, you can use Lighthouse accessibility checks and axe to validate WCAG 2.1 POUR requirements. These tools automate detection of keyboard operability issues, perceivable alternatives, and robust semantic markup, while manual test checklists complete the validation for screen reader and keyboard interactions.