qa-accessibility

Audits web interfaces for WCAG 2.2 AA compliance using axe-core and Lighthouse checks.

2|1|Updated May 27, 2025

Search Tags:#accessibility #wcag #lighthouse #axe-core #aria #qa testing #keyboard testing

Ready to run

npx skills add https://github.com/VirtoCommerce/vc-mcp-testing-module --skill qa-accessibility

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-accessibility
Source: https://github.com/VirtoCommerce/vc-mcp-testing-module/tree/main/skills/qa-accessibility
Command: npx skills add https://github.com/VirtoCommerce/vc-mcp-testing-module --skill qa-accessibility

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps QA teams identify accessibility barriers in web applications by combining automated checks with manual verification guidance against WCAG 2.2 Level AA requirements.

Core Features & Use Cases

WCAG 2.2 AA Audits: Evaluate pages and user flows across POUR principles, including new 2.2 criteria such as focus visibility, target size, and accessible authentication.
Multi-layer Testing Guidance: Coordinate axe-core scans, Lighthouse accessibility checks, keyboard navigation reviews, ARIA validation, and dynamic state rescans.
Use Case: Audit an e-commerce checkout flow to find keyboard traps, contrast failures, missing labels, focus issues, and accessibility defects before release.

Quick Start

Use the qa-accessibility skill to perform a WCAG 2.2 AA audit of the checkout page and generate a severity-grouped accessibility report.

Frequently Asked Questions about qa-accessibility

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

FAQPage Schema

How do I audit a website for WCAG 2.2 AA accessibility compliance?▼

Audit a website for WCAG 2.2 AA compliance by combining axe-core scans, Lighthouse checks, keyboard navigation verification, and ARIA assessments. This process identifies usability barriers like missing labels and focus issues across storefronts, admin panels, and user journeys.

What is the best way to test keyboard navigation and avoid traps during an accessibility audit?▼

Testing keyboard navigation requires verifying tab order and checking for keyboard traps across dynamic states. The audit performs keyboard navigation verification alongside ARIA validation and dynamic state rescans to ensure interactive elements remain accessible to assistive technology users.

Can I use axe-core and Lighthouse to find contrast failures and missing ARIA labels?▼

Yes, axe-core analysis and Lighthouse accessibility checks are used together to detect contrast failures, missing labels, and ARIA defects. These automated checks are coordinated with manual testing scenarios to validate complete user journeys against WCAG criteria.

Does WCAG 2.2 Level AA testing cover focus visibility and target size requirements?▼

WCAG 2.2 Level AA testing evaluates pages across POUR principles, specifically including new 2.2 criteria such as focus visibility, target size, and accessible authentication. This ensures modern storefronts and admin panels meet the latest accessibility standards.

How do I rescan dynamic web states for accessibility defects during a checkout flow audit?▼

Rescan dynamic web states for accessibility defects by applying axe-core analysis and ARIA assessment after state changes. The audit workflow includes dynamic state rescans to catch emerging usability barriers in interactive flows like e-commerce checkout processes.

When do I need manual testing scenarios instead of just automated accessibility checks?▼

Manual testing scenarios are needed alongside automated checks to validate complete user journeys and verify keyboard navigation. While axe-core and Lighthouse find code-level defects, manual verification confirms real-world usability barriers for assistive technology users.