wcag-audit-patterns

Audit web pages for WCAG 2.2 violations with automated and manual checks.

6|4|Updated Nov 1, 2025
One-click install
npx skills add https://github.com/Montte-erp/montte-nx --skill wcag-audit-patterns-montte-erp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wcag-audit-patterns
Source: https://github.com/Montte-erp/montte-nx/tree/main/.agents/skills/wcag-audit-patterns
Command: npx skills add https://github.com/Montte-erp/montte-nx --skill wcag-audit-patterns-montte-erp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auditing web content for accessibility issues is time-consuming and incomplete when relying only on automated tools or ad-hoc manual checks. This Skill provides a structured audit workflow combining automated scans, manual verification checklists, and prioritized remediation guidance so teams can reach WCAG 2.2 conformance more reliably and communicate fixes clearly.

Core Features & Use Cases

  • Automated testing guidance: Integrates axe-core and CLI tooling recommendations to detect common programmatic violations such as missing alt text, contrast failures, and ARIA issues.
  • Manual verification checklists: POUR-based checklists and targeted manual tests for keyboard navigation, meaningful sequence, and usability with assistive technologies.
  • Remediation patterns: Concrete code and markup patterns for fixes (labels, focus management, contrast adjustments, ARIA roles) and prioritization by impact and WCAG success criteria.
  • Use Cases: Pre-launch accessibility QA for public websites, remediation sprints for design systems, and evidence-based reports for legal/compliance reviews.

Quick Start

Run a full WCAG 2.2 accessibility audit on your site URL and produce a prioritized remediation report that includes automated violations, manual checks, and recommended code fixes.

Frequently Asked Questions about wcag-audit-patterns

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

FAQPage Schema
How do I audit a web application for WCAG 2.2 accessibility violations?

Auditing for WCAG 2.2 accessibility violations requires combining automated axe-core scans with POUR-based manual checklists. This structured workflow identifies missing alt text and contrast failures, generating a prioritized remediation report with actionable code fixes.

What is included in a WCAG 2.2 accessibility compliance report?

A WCAG 2.2 compliance report includes axe-core compatible violation outputs, POUR-based manual verification checklists, and prioritized remediation guidance. It references specific WCAG success criteria to support legal reviews and QA remediation sprints.

Can I use axe-core and Playwright for automated accessibility testing of single-page applications?

Yes, you can use axe-core and Playwright for automated accessibility testing on single-page applications. The Skill provides CLI tooling recommendations to detect programmatic violations like missing labels and ARIA issues during development.

How do I fix keyboard navigation and contrast issues for WCAG compliance?

To fix keyboard navigation and contrast issues for WCAG compliance, apply concrete remediation patterns like focus management adjustments and contrast ratio tuning. The Skill provides prioritized fixes mapped to specific WCAG success criteria.

Does automated accessibility testing catch all WCAG 2.2 violations?

Automated accessibility testing does not catch all WCAG 2.2 violations. It detects programmatic issues like missing alt text, but manual verification using POUR-based checklists is required to validate meaningful sequence and assistive technology usability.

What is the best way to prepare a design system for an accessibility remediation sprint?

The best way to prepare for an accessibility remediation sprint is auditing the component library for WCAG 2.2 violations. This generates prioritized remediation guidance with actionable markup patterns for labels, ARIA roles, and contrast.