accessibility

Audit web interfaces against WCAG 2.2 accessibility standards.

214|7|Updated May 29, 2026
One-click install
npx skills add https://github.com/anolilab/lunora --skill accessibility-anolilab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/anolilab/lunora/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/anolilab/lunora --skill accessibility-anolilab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the challenge of ensuring web content is usable by everyone, including people with disabilities, by providing a structured framework for auditing and improving accessibility.

Core Features & Use Cases

  • WCAG 2.2 Compliance: Provides comprehensive guidelines to meet A, AA, and AAA conformance levels.
  • Practical Patterns: Offers copy-paste-ready code for common accessibility requirements like focus traps, skip links, and error handling.
  • Use Case: Use this Skill to perform a manual accessibility audit on a new UI component, ensuring it meets color contrast requirements, has proper keyboard navigation, and includes correct ARIA roles.

Quick Start

Use the accessibility skill to perform a comprehensive WCAG 2.2 audit on the current project and identify critical compliance gaps.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I audit web accessibility for WCAG 2.2 compliance?

To audit web accessibility, apply WCAG 2.2 guidelines to interface components and content structures. This process involves automated Lighthouse testing and manual verification of keyboard navigation, screen reader compatibility, and color contrast to ensure A, AA, and AAA conformance.

What is the best way to check color contrast and keyboard navigation in a new UI component?

Checking color contrast and keyboard navigation requires manual verification against WCAG 2.2 standards. You can use standardized testing checklists to evaluate interface components, ensuring proper focus traps, skip links, and correct ARIA roles for screen reader compatibility.

How do I fix common ARIA roles and error handling issues for screen readers?

Fixing ARIA roles and error handling issues involves applying standardized code patterns designed for screen reader compatibility. You can implement copy-paste-ready solutions for common accessibility requirements to meet WCAG 2.2 A, AA, and AAA conformance levels.

Does this accessibility audit cover both automated testing and manual screen reader verification?

Yes, the accessibility audit covers both automated and manual verification. It supports tasks ranging from automated Lighthouse testing to manual verification of keyboard navigation and screen reader compatibility, ensuring comprehensive compliance with WCAG 2.2 guidelines.

When do I need to verify WCAG 2.2 AA and AAA conformance levels for web content?

You need to verify WCAG 2.2 AA and AAA conformance levels when ensuring web content is usable by everyone, including people with disabilities. This structured framework audits interface components and content structures to identify and resolve critical compliance gaps.

Why does my web interface fail keyboard navigation and focus trap tests?

Web interfaces often fail keyboard navigation and focus trap tests due to non-compliant code patterns. Applying standardized WCAG 2.2 guidelines and practical accessibility patterns for focus management and ARIA roles resolves these critical compliance gaps.