What is the four-step methodology used in this skill?

The skill uses: (1) run automated scans with axe, Lighthouse, and WAVE to collect initial findings; (2) perform manual checks for keyboard navigation, focus order, and screen reader flows that automated tools can't catch; (3) map each issue to a specific WCAG success criterion, severity level, and remediation guidance; and (4) re-test after fixes and document residual risk and current compliance status.

Why does this skill require manual testing in addition to automated scanning?

The skill explicitly treats automated scanning alone as insufficient because manual verification of keyboard and screen-reader behavior is required to catch issues that automated tools can't reliably detect. Manual testing is a mandatory second pass, not optional.

What should I NOT use this skill for?

Do not use it when you need legal advice or formal legal certification (it produces technical findings, not legal opinions), when you only want a quick automated scan without manual verification, or when you lack access to the UI or source code needed to perform remediation.

What does the output of this skill include?

The output is a findings report that maps each issue to its WCAG 2.2 criterion, severity level, and remediation guidance, followed by a re-test cycle documenting what was fixed, what residual risk remains, current compliance status, and preserved test-step evidence for an audit trail.

What automated tools does this skill use for scanning?

The skill uses axe, Lighthouse, and WAVE for initial automated findings, supplemented by manual keyboard-navigation and screen-reader testing.

Skill

Audit Web Content for WCAG Compliance

Name: WCAG Audit Patterns
Availability: OnlineOnly
Author: Antigravity

WCAG 2.2 accessibility audit guide combining automated scans and manual checks with WCAG-criterion remediation mapping.

Get skill

Antigravity

Own this? Claim it

Spark score

out of 100

Updated 3 days ago

Version 15.5.1

Add to Favorites

Why it matters

Ensure your web content meets WCAG 2.2 accessibility standards. This asset provides a comprehensive guide for auditing, identifying violations, and implementing remediation strategies to achieve compliance.

Outcomes

What it gets done

Conduct thorough accessibility audits using automated and manual checks.

Map identified issues to specific WCAG criteria and assign severity.

Provide actionable remediation guidance for fixing accessibility violations.

Document compliance status and residual risks after fixes.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-wcag-audit-patterns | bash

Overview

WCAG Audit Patterns

Combines automated scans (axe, Lighthouse, WAVE) with manual keyboard and screen-reader testing, mapping each finding to a WCAG 2.2 criterion, severity, and remediation guidance. Use when conducting an accessibility audit or fixing WCAG violations, not as a substitute for legal certification.

What it does

A guide to auditing web content against WCAG 2.2 guidelines with actionable remediation strategies, combining automated and manual testing. Its four-step process: run automated scans using axe, Lighthouse, or WAVE to collect initial findings, perform manual checks such as keyboard navigation, focus order, and screen reader flows that automated tools can't catch, map each issue to its specific WCAG success criterion, severity, and remediation guidance, and re-test after fixes while documenting residual risk and compliance status. It explicitly warns against claiming legal compliance without expert review, and requires keeping evidence of test steps and results for an audit trail.

When to use - and when NOT to

Use when conducting an accessibility audit, fixing WCAG violations, implementing accessible components, preparing for an accessibility lawsuit, meeting ADA or Section 508 requirements, or working toward VPAT compliance. Not for legal advice or formal certification, not for a quick automated scan alone without manual verification, and not usable when there's no access to the UI or source needed to actually remediate findings.

Inputs and outputs

Input is the web content or component to audit plus access to the live UI or source for remediation. Output is a findings list mapping each issue to a WCAG criterion, severity, and remediation guidance, plus a re-test record documenting residual risk and current compliance status. Detailed patterns, checklists, and templates live in resources/implementation-playbook.md.

Integrations

Named automated scanning tools are axe, Lighthouse, and WAVE, combined with manual keyboard-navigation and screen-reader testing; references its own companion resource, resources/implementation-playbook.md, for detailed patterns and checklists.

Who it's for

Accessibility auditors and developers who need to combine automated scan results with manual verification and map findings to specific WCAG criteria, rather than relying on an automated scan alone.

FAQ

Common questions

Discussion