skills.rest
johnnystefan
johnnystefanCOMMUNITY
Explore all skills by this author →
GitHub

accessibility

Audit web experiences for WCAG 2.2 accessibility compliance gaps.

Updated Mar 26, 2026
Search Tags:#accessibility#a11y#wcag#screen-reader#color-contrast#aria#keyboard-navigation
One-click install
npx skills add https://github.com/johnnystefan/test-saas-business --skill accessibility-johnnystefan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/johnnystefan/test-saas-business/tree/main/skills/accessibility
Command: npx skills add https://github.com/johnnystefan/test-saas-business --skill accessibility-johnnystefan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manual accessibility compliance with WCAG 2.2 is difficult; this skill provides structured criteria, actionable guidance, and testing steps so dev and design teams can eliminate perceivable, operable, understandable, and robust barriers before launch.

Core Features & Use Cases

  • POUR-based guidance: Breaks WCAG principles into perceivable, operable, understandable, and robust sections with color contrast, keyboard navigation, form labeling, ARIA usage, and live-region instructions.
  • Testing checklist: Combines automated Lighthouse/axe commands with manual checks for keyboard navigation, screen readers, zoom, contrast, reduced motion, and focus order to confirm compliance.
  • Use Case: Run this skill while reviewing the admin or customer app to enforce skip links, descriptive alt text, focus visibility, drag alternatives, and accessible authentication choices in line with WCAG 2.2.

Quick Start

Ask for a WCAG 2.2 accessibility audit of the admin dashboard and request fixes for color contrast, keyboard navigation, and ARIA usage.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I check my web UI for WCAG 2.2 accessibility compliance?▼

Check WCAG 2.2 accessibility compliance by auditing perceivable, operable, understandable, and robust interactions against criteria for color contrast, keyboard navigation, skip links, media alternatives, and ARIA semantics.

What is included in a manual WCAG 2.2 accessibility testing checklist?▼

A manual WCAG 2.2 accessibility testing checklist includes checks for keyboard navigation, screen readers, zoom, contrast, reduced motion, and focus order to confirm compliance and eliminate usage barriers.

How do I fix keyboard navigation and focus visibility issues for screen readers?▼

Fix keyboard navigation and focus visibility for screen readers by enforcing skip links, descriptive alt text, clear focus indicators, and proper ARIA semantics to ensure operable and robust interactions.

Can I use automated Lighthouse and axe checks for WCAG 2.2 compliance?▼

You can use automated Lighthouse and axe checks for WCAG 2.2 compliance by combining them with manual checks for keyboard navigation, screen readers, zoom, contrast, reduced motion, and focus order.

Does WCAG 2.2 require accessible authentication and drag alternatives?▼

WCAG 2.2 does require accessible authentication choices and drag alternatives, alongside specifications for reduced motion preferences, focus indicators, and descriptive alt text to ensure operable interfaces.

Related Skills

Explore More Software Engineering Skills→
runkidsrunkids
11

accessibility

Audit web accessibility against WCAG 2.1 and generate remediation plans.

Community
Basic
ryan-nguyen-01ryan-nguyen-01
4

skill-ui-accessibility

Analyze web UI structure, semantics, and ARIA usage for accessibility gaps.

Community
Advanced
hulusi-tunchulusi-tunc
3

accessibility-test-plan

Create accessibility testing plans for web and mobile applications.

Community
Advanced
civictechdccivictechdc
1

wcag-audit-patterns

Automate WCAG 2.2 accessibility audits and remediation guidance for websites.

Official
Advanced