WCAG 2.2 Audit Checklist

Scope a representative sample

List the page templates, common components and complete user flows to review. Include sign-in, form errors, dialogs, menus, downloads and relevant mobile layouts. A checklist limited to the home page cannot describe an entire transactional service. Record the tested build and the sample selection rationale.

Automated and manual work

Use the existing browser-only HTML checker as one source of findings. It does not execute the submitted page’s scripts or fetch external styles. Keyboard use, meaningful text alternatives, screen-reader behaviour, captions and workflow completion require additional review of the running service by a qualified tester.

A worksheet with evidence

Use the linked existing guided checklist for the criterion-level review. For each applicable test, record the page/state, method, result, evidence reference, tester and date. Leave not checked visible. Not applicable needs a reason tied to scope; it must not become a shortcut for a test that has not been performed.

Worked form example

A form has a correctly associated label but an error message that is not announced. The label check can pass while the error-state review fails. Record both observations with the exact interaction, assistive technology and screenshot or recording reference. Assign remediation to the form component owner and retest the corrected error state.

Closing the audit

Group repeated defects by component without erasing the pages affected. Keep open issues, accepted exceptions and retest results distinct. A report with zero automated failures can still have manual findings. Save the original and final evidence under the organisation’s records controls.