skills.rest
legions-developer
legions-developerCOMMUNITY
Explore all skills by this author →
Website𝕏@legionsdevGitHub

accessibility

Audit web interfaces for WCAG 2.2 accessibility compliance and improvements.

885|108|Updated Apr 30, 2025
Search Tags:#accessibility#screen reader#keyboard navigation#wcag 2.2#color contrast#aria#lighthouse audit
One-click install
npx skills add https://github.com/legions-developer/invoicely --skill accessibility-legions-developer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/legions-developer/invoicely/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/legions-developer/invoicely --skill accessibility-legions-developer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you identify and fix common accessibility gaps so users—especially people using assistive technologies—can perceive, operate, and understand your web content.

Core Features & Use Cases

  • WCAG 2.2-aligned guidance: Covers the POUR principles (Perceivable, Operable, Understandable, Robust) and maps issues to success criteria.
  • Actionable fixes with examples: Provides concrete HTML, CSS, and JavaScript patterns for real UI problems like missing labels, poor focus handling, and insufficient contrast.
  • Audit-ready checklists: Includes testing steps using Lighthouse and axe plus manual verification guidance for keyboard, screen readers, zoom, and reduced motion.

Quick Start

Ask: "Audit this page for WCAG 2.2 accessibility issues and return prioritized fixes for keyboard navigation, form labels, focus states, and color contrast."

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 app for WCAG 2.2 accessibility issues?▼

To audit web app accessibility for WCAG 2.2 compliance, evaluate UI components against POUR principles, test keyboard navigation and screen reader support, and map issues to success criteria for assistive technology compatibility.

What is the best way to fix keyboard navigation and focus state issues?▼

Fix keyboard navigation issues by implementing concrete HTML and JavaScript patterns to manage focus handling, ensuring logical tab order and visible focus states that meet WCAG operability success criteria for users.

How do I check color contrast and ARIA patterns for screen reader compatibility?▼

Check color contrast and ARIA patterns by applying common ARIA roles and verifying contrast ratios against WCAG conformance levels, ensuring screen readers can accurately perceive and announce web interface elements.

Can I target specific WCAG conformance levels like A, AA, or AAA during an audit?▼

Yes, you can target specific WCAG conformance levels (A, AA, or AAA) during an audit to align testable recommendations with the desired success criteria and ensure web content meets appropriate accessibility standards.

How do I test web interfaces for users with disabilities using Lighthouse and axe?▼

Test web interfaces for users with disabilities by running Lighthouse and axe audits, then performing manual verification of keyboard operability, screen reader feedback, zoom levels, and reduced motion preferences to resolve usability barriers.

Related Skills

Explore More Design & Creative Skills→
harivansh-afkharivansh-afk
3

web-design-guidelines

Audit HTML, CSS, and JavaScript UI code against Web Interface Guidelines.

Community
Intermediate
89jobrien89jobrien
4

web-accessibility

Audit web content for WCAG 2.1/2.2 conformance and accessibility issues.

Community
Advanced
mae616mae616
9

accessibility-engineer

Enforce accessible UI with semantic HTML and minimal ARIA.

Community
Basic
Tahona-AITahona-AI

wcag-audit-patterns

Audit website compliance with WCAG 2.2 standards using automated scripts.

Official
Intermediate