gsp-accessibility-audit

A WCAG accessibility audit scans design screen chunks and codebases to identify compliance gaps in HTML, ARIA attributes, keyboard support, and visual contrast, generating detailed reports and actionable fix lists.

Yes, you can generate a formal accessibility compliance statement by feeding previous audit results into the tool, producing a formal document that outlines your project's WCAG conformance status.

You can use design audit mode to scan design screen chunks, identifying potential barriers early and producing detailed accessibility reports and fix lists to resolve compliance gaps before development.

Yes, the WCAG audit requires read and write file access to scan your codebase and design chunks, spawn the auditor agent, and support user prompts to resolve ambiguities during the workflow.

The best way to resolve ambiguities during an automated accessibility audit is using a user-guided workflow that prompts you with questions, ensuring accurate WCAG compliance verification and directing next steps.

An automated WCAG compliance tool provides a unified way to verify designs and code, preventing compliance gaps and costly rework across development phases by systematically analyzing ARIA, contrast, and keyboard support.