forms-errors-accessibility-audit

Inventory every form state (initial, invalid, submitting, success, failure), then verify labels, instructions, required and invalid states, error identification, validation timing, keyboard behavior, and recovery. This Skill walks through each area and produces a structured findings report with WCAG 2.2 mappings.

Verify each error identifies the affected field in text, is programmatically associated with the field, and is announced via status messages or focus movement without relying on color alone. The audit separates confirmed code findings from announcements that require live screen-reader testing.

No. The audit maps findings to relevant WCAG 2.2 criteria using wording like "maps to" or "requires verification against," but a scoped audit or automated scan never establishes full conformance. The report explicitly states this limitation.

Yes. It audits whatever evidence exists, such as source code, templates, screenshots, or design briefs, and moves unverifiable behavior like focus management and screen-reader announcements into a manual-test requirements list with executable steps.

Automation confirms detectable defects like missing labels or invalid ARIA, but cannot infer keyboard operability, screen-reader announcement quality, or recovery behavior. Those checks are recorded as manual-test requirements with preconditions, steps, and expected accessible behavior.