accessibility-audit

To audit UI components for WCAG compliance, this Skill runs a visual analysis phase to detect color contrast gaps, keyboard navigation issues, and missing alternative text. It then applies phase-based component checklists to ensure consistent accessibility conformance across pages.

The best way to check color contrast and keyboard navigation is by running a visual accessibility evaluation during design reviews. This process surfaces WCAG issues and usability defects early, generating reporting templates to support immediate fixes before launch.

Yes, you can use a phase-based checklist to ensure pre-launch accessibility verification. This workflow defines specific component and page checklists, enabling teams to systematically identify and fix accessibility issues and generate comprehensive audit reports.

Yes, this accessibility audit works for both development sprints and pre-launch verification. It defines a phase-based workflow applicable at either stage to identify WCAG conformance issues, evaluate usability, and generate structured reporting templates for tracking results.

Your UI accessibility audit needs a storage plan for audit results to maintain consistency across development sprints. Defining a storage plan ensures that visual analysis outputs, component checklists, and comprehensive reporting templates are tracked and referenced for future pre-launch verification.

With an a11y audit, you can identify and fix WCAG issues like insufficient color contrast, keyboard navigation gaps, and missing meaningful alternative text. The audit applies component checklists to surface these usability defects during design reviews and development sprints.