Run this check →

New accounts start with 40 free credits.

Check a web page against WCAG 2.2 A and AA

Web Accessibility — WCAG 2.2

Last updated: 29 September 2026

WHAT IT CHECKS

A web page's HTML or component code, against 120 rules covering 54 of the 55 WCAG 2.2 Level A and AA success criteria — including name, role and value; labels; page titles; focus visibility; redundant entry; accessible authentication; contrast; keyboard access; and time-based media.

WHERE THE RULES COME FROM

The World Wide Web Consortium (W3C): WCAG 2.2 and its supporting documents.

WHAT IT DOES NOT CHECK

  • Success criterion 3.3.4 Error Prevention (Legal, Financial, Data) is not covered, and is listed on every report.
  • A partial check, not an AA conformance audit. It reads what you give it; it does not operate a live page with a keyboard or screen reader.

WHAT YOU GET BACK

  • Each gap it finds, with the rule it fails and the source text that rule was taken from, quoted, so you can check it yourself.
  • Replacement wording for each finding, and a corrected copy of your document to download.
  • The pack's declared gaps, printed on every report, so you know what was not checked.

HOW TO RUN IT

In the browser. Sign in at https://vera.ink/verify, paste or upload the document, and choose this pack. New accounts start with 40 credits; a check costs 3 credits up to about 4,500 words.

From your AI assistant. vera.ink is an MCP server. Connect it to Claude Code or Cursor and ask your assistant to check a file against this pack: https://vera.ink/developers

GOOD TO KNOW

  • vera.ink only reports findings it can tie to a rule in this pack, and quotes the source text so you can check it. Anything it can't tie to a rule is dropped from the report.
  • It is a review aid, not legal advice or a certification. Read each finding before you act on it.

More checks: https://vera.ink/check