accessibility

Audit digital interfaces for WCAG 2.2 AA compliance issues.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Vincri126/MCO-Template --skill accessibility-vincri126
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/Vincri126/MCO-Template/tree/main/.orchestrator/skills/accessibility
Command: npx skills add https://github.com/Vincri126/MCO-Template --skill accessibility-vincri126

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires htmlhint, wcag-contrast, @axe-core/cli, lighthouse, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Accessibility regressions and compliance gaps slow product launches and exclude users when WCAG 2.2 AA requirements go unchecked. This skill centralizes audit knowledge, testing checklists, and guidance so every interface review highlights the most urgent barriers before release.

Core Features & Use Cases

  • WCAG 2.2 AA playbook: Covers perceivable, operable, understandable, and robust principles along with color contrast ratios, keyboard navigation patterns, and semantic markup recommendations.
  • QA gate automation: Provides scripts that validate HTML, run wcag-contrast, axe-core, Lighthouse, and WAVE scans so engineers can catch violations in CI before merges.
  • Reference materials: Ships aria-patterns, qa-gates, and testing-protocol documents that teams can cite when designing modals, forms, dropdowns, or live regions.

Quick Start

Ask the accessibility skill to audit the landing page for WCAG 2.2 AA violations and summarize remediation steps.

Frequently Asked Questions about accessibility

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

FAQPage Schema
How do I audit a web interface for WCAG 2.2 AA compliance violations?▼

WCAG 2.2 AA compliance audits validate color contrast ratios, keyboard navigation patterns, and semantic markup against perceivable, operable, understandable, and robust principles. Running axe-core and Lighthouse scans highlights urgent accessibility barriers and regressions before product launch.

Can I automate accessibility testing in CI to catch WCAG violations before merges?▼

Automated accessibility QA gates execute htmlhint, wcag-contrast, axe-core, and Lighthouse scripts within CI pipelines. Running these tools validates HTML structure and catches WCAG 2.2 AA violations before code merges, preventing accessibility regressions.

What WCAG 2.2 AA color contrast ratios do I need for digital interfaces?▼

WCAG 2.2 AA color contrast requirements mandate specific minimum ratios for text and graphical elements. Running wcag-contrast and Lighthouse scans during interface audits validates these ratios, ensuring perceivable content for users with visual impairments.

How do I implement ARIA patterns for modals, forms, and live regions?▼

Implementing ARIA patterns for modals, forms, and live regions requires following semantic markup recommendations and testing protocol documents. Proper ARIA usage ensures keyboard navigation operability and screen reader compatibility across dynamic web application components.

Does axe-core work with Lighthouse for comprehensive web accessibility reviews?▼

Axe-core and Lighthouse work together to provide comprehensive web accessibility reviews. Running both tools alongside wcag-contrast covers semantic markup validation, keyboard navigation audits, and color contrast checks for full WCAG 2.2 AA compliance coverage.

Why does my keyboard navigation test fail WCAG operable principle requirements?▼

Keyboard navigation tests fail WCAG operable principle requirements when interactive elements lack proper focus management, semantic markup, or ARIA roles. Running axe-core audits identifies missing focus states and keyboard traps that block operable interface interactions.