Accessibility · Checklist

WCAG 2.2 Audit + VPAT®/ACR Prep Checklist, for the EAA era.

Audit against WCAG 2.2 and prepare a VPAT®/ACR with the European Accessibility Act's enforcement already live — organized by the four POUR principles.

Mapped to current published standards & statute text
18
Checklist items, each with a test procedure & evidence example
5
Stages, organized the way a real implementation unfolds
Free to use. Work through it here, no form needed. To get your readiness score, submit it for expert review below.
Expert review

Get your readiness score

Work through the checklist, then submit it — an expert scores it using Self-Compliance and emails you the result.

Check off at least one item below to unlock
Open "How to verify this" on any item for the exact test procedure & evidence an auditor would want Progress saves only in this browser — nothing is sent anywhere until you submit it for review
0 of 18 items checked off
Browsing:
  • How to verify this →

    Test procedureRun an automated scan (e.g. axe, WAVE) plus a manual pass over non-text content; verify decorative images use empty alt, not missing alt.

    Practical example / evidenceScan report plus a manually reviewed sample of image alt text.

  • How to verify this →

    Test procedureMeasure contrast ratios with a contrast-checker tool against 1.4.3/1.4.11 thresholds across key screens, including hover/focus states.

    Practical example / evidenceContrast-checker report with pass/fail per screen.

  • How to verify this →

    Test procedureReview error states, charts and status indicators with a color-blindness simulator to confirm meaning survives without color.

    Practical example / evidenceSimulator screenshots or review notes per affected component.

  • How to verify this →

    Test procedureSpot-check a sample of video/audio assets for caption accuracy and transcript completeness.

    Practical example / evidenceCaption files (.vtt/.srt) and transcripts for sampled media.

Stage 1 of 5
  • How to verify this →

    Test procedureUnplug the mouse and complete each key user flow using Tab/Shift+Tab/Enter/Space/Arrow keys only.

    Practical example / evidenceKeyboard-only test walkthrough notes or recording per flow.

  • How to verify this →

    Test procedureTab through every interactive element and confirm the focus ring remains visible, including inside modals and sticky headers.

    Practical example / evidenceScreenshots of focus state on each component type.

  • How to verify this →

    Test procedureTest every drag interaction (sliders, reordering, swipe) for a tap/click-based alternative that achieves the same result.

    Practical example / evidenceTest notes confirming a single-pointer alternative per drag interaction.

  • How to verify this →

    Test procedureTab continuously through the full page and confirm focus never gets stuck and follows the visual/logical reading order.

    Practical example / evidenceTab-order walkthrough notes flagging any trap or out-of-order jump.

Stage 2 of 5
  • How to verify this →

    Test procedureWalk a multi-step form and confirm previously entered data (name, address) is carried forward or auto-filled, not re-asked.

    Practical example / evidenceScreen recording of the multi-step flow showing data persistence.

  • How to verify this →

    Test procedureReview the login flow for a non-cognitive alternative (password manager support, email link, biometric) alongside any puzzle/memory step.

    Practical example / evidenceLogin flow documentation listing the available authentication alternatives.

  • How to verify this →

    Test procedureSubmit invalid data in every form field and confirm the error names the specific field and what's wrong with it.

    Practical example / evidenceScreenshots of error states per form field.

  • How to verify this →

    Test procedureCompare navigation labels and placement across five representative pages for consistency.

    Practical example / evidencePage-by-page navigation audit notes.

Stage 3 of 5
  • How to verify this →

    Test procedureRun the page through an HTML validator and an accessibility tree inspector to check semantic elements are used before reaching for ARIA.

    Practical example / evidenceValidator report and accessibility-tree export.

  • How to verify this →

    Test procedureInspect the accessibility tree in dev tools for each custom component and confirm ARIA attributes match actual behavior (e.g. aria-expanded toggles correctly).

    Practical example / evidenceAccessibility-tree screenshots per custom component.

  • How to verify this →

    Test procedureComplete each key user flow using NVDA, JAWS or VoiceOver and confirm announcements make sense without sight.

    Practical example / evidenceScreen-reader test session notes or recording.

Stage 4 of 5
  • How to verify this →

    Test procedureConfirm the VPAT template version matches the standard your buyer or regulator actually requires before filling it in.

    Practical example / evidenceVPAT template cover page showing edition/version used.

  • How to verify this →

    Test procedureSpot-check ten success criteria and confirm the remark cites specific evidence (a test result), not a generic statement.

    Practical example / evidenceCompleted ACR with remarks column populated per criterion.

  • How to verify this →

    Test procedureCross-check every non-'Supports' rating in the ACR has a corresponding line item in the remediation roadmap.

    Practical example / evidenceRemediation roadmap with target dates mapped to ACR line items.

Stage 5 of 5

Frequently asked questions

Does an accessibility overlay satisfy these checklist items?

No. Overlays operate on top of the page and can't fix underlying markup, keyboard operability or focus-management issues — they're widely found not to achieve real WCAG conformance and don't reduce legal risk.

Do we need WCAG 2.2 or is 2.1 still acceptable?

Most current regulatory references point to WCAG 2.1 or 2.2 depending on jurisdiction and when the requirement was set; 2.2 is the more current standard and includes criteria (like focus visibility and accessible authentication) that address real, frequently-cited failures — worth meeting even where only 2.1 is formally required.

What's the difference between a VPAT and an ACR?

VPAT is the template format; once filled in for your specific product, the completed document is called an Accessibility Conformance Report (ACR). People often use the terms interchangeably.