accessibility

Audit and improve web accessibility following WCAG 2.2 guidelines and ARIA patterns.

Updated May 28, 2026
One-click install
npx skills add https://github.com/qbstabletampa-creator/firmware-foundation-studios --skill accessibility-qbstabletampa-creator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/qbstabletampa-creator/firmware-foundation-studios/tree/main/archive/apps/manna-catch/.agents/skills/accessibility
Command: npx skills add https://github.com/qbstabletampa-creator/firmware-foundation-studios --skill accessibility-qbstabletampa-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Web interfaces often exclude users with disabilities due to missing alt text, poor color contrast, keyboard traps, and incorrect ARIA usage. This Skill provides WCAG 2.2-based guidance to audit and fix accessibility issues across HTML, CSS, and JavaScript. ## Core Features & Use Cases - WCAG 2.2 Auditing: Covers all POUR principles with conformance levels A, AA, and AAA, including new 2.2 criteria like target size, dragging movements, and accessible authentication. - Copy-Paste Code Patterns: Ready-to-use implementations for modal focus traps, skip links, form labels, error handling, ARIA tabs, and live regions. - Testing Guidance: Automated testing with Lighthouse and axe-core plus manual checklists for keyboard navigation, screen readers, zoom, and reduced motion. - Use Case: When asked to make a checkout form accessible, apply the form labels and error handling patterns, verify color contrast ratios, and test keyboard navigation end to end. ## Quick Start Audit this page for WCAG 2.2 compliance and fix any accessibility issues you find.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I make a website WCAG 2.2 compliant?▼

Audit against the four POUR principles: perceivable, operable, understandable, and robust. Fix critical issues first, such as missing form labels, missing alt text, insufficient contrast, keyboard traps, and invisible focus indicators, then verify with Lighthouse or axe-core.

What color contrast ratio is required for WCAG AA?▼

WCAG AA requires 4.5:1 contrast for normal text and 3:1 for large text (18px or 14px bold and above). UI components and graphical objects need at least 3:1. Level AAA raises normal text to 7:1.

How do I trap focus inside a modal dialog?▼

Cycle Tab and Shift+Tab between the first and last focusable elements inside the modal and close on Escape. The native HTML dialog element handles focus trapping automatically, so prefer it when browser support allows.

Should I use ARIA roles or native HTML elements?▼

Prefer native HTML elements like button, input, and nav because they include built-in keyboard behavior and semantics. Use ARIA roles and states only when no native equivalent exists, such as custom tablists or live region notifications.

What changed from WCAG 2.1 to WCAG 2.2?▼

WCAG 2.2 removed criterion 4.1.1 Parsing and added nine new criteria, including focus not obscured, dragging movements, target size minimum of 24 by 24 CSS pixels, consistent help, redundant entry, and accessible authentication.

How do I test accessibility with screen readers?▼

Test with VoiceOver on Mac (Command+F5 to start) or NVDA on Windows (Ctrl+Alt+N). Navigate by headings, links, and landmarks, verify focus order matches visual order, and confirm dynamic updates are announced via aria-live regions.