{"canonical_url":"https://engineer.company/glossary/wcag/","content_markdown":"# WCAG 2.2\n\n## What it is\n\nWCAG 2.2, the Web Content Accessibility Guidelines version 2.2, is the W3C standard that spells out,\nin testable statements, what web content has to do so that people with disabilities can use it. It\nbecame a W3C Recommendation in October 2023, and the current edition is dated 12 December 2024. It\nfollows WCAG 2.0 from 2008 and 2.1 from 2018, and in conversation it is usually just WCAG. A WCAG 3\nis being developed alongside it as a separate, multi-year effort; 2.2 is the version that contracts\nand audits work from today.\n\nThe document is built in layers. Four principles say content must be perceivable, operable,\nunderstandable and robust. Under them sit 13 guidelines, which state goals and are not testable.\nUnder each guideline are the success criteria, the part that counts: each has a number such as\n1.4.3, a short name such as Contrast (Minimum), a level, and a sentence that a page either meets or\nfails. Around this normative text the W3C publishes an Understanding document for every criterion\nand a library of techniques and documented failures. Those are informative: a page that meets a\ncriterion by another route still meets it.\n\nThere are three levels. Level A is the minimum, AA adds the criteria most organisations are asked\nto meet, and AAA is the strictest. A level is cumulative and met in full or not at all: for Level\nAA, in the standard's own words, \"the web page satisfies all the Level A and Level AA success\ncriteria, or a Level AA conforming alternate version is provided.\" Conformance belongs to full\npages, never to part of one, and to complete processes. When a purchase runs across five pages, all\nfive must conform at a level for any of them to.\n\nVersion 2.2 added nine criteria and retired one. The additions at Levels A and AA are 2.4.11 Focus\nNot Obscured (Minimum), 2.5.7 Dragging Movements, 2.5.8 Target Size (Minimum), 3.2.6 Consistent\nHelp, 3.3.7 Redundant Entry and 3.3.8 Accessible Authentication (Minimum). The other three, 2.4.12,\n2.4.13 and 3.3.9, sit at AAA. 4.1.1 Parsing is marked obsolete and removed, because assistive\ntechnology no longer parses HTML directly. The rest carries over from 2.1 essentially unchanged, so\na site that conforms to 2.2 also conforms to 2.1.\n\n## Why it matters\n\nWCAG turns \"make it accessible\" into a list somebody can check, and the standard names what its\ntestable criteria are for: design specifications, purchasing, regulation and contractual\nagreements. For a buyer, the decision that matters is one sentence in the contract. \"Accessible\"\ncan be argued about forever. \"WCAG 2.2 Level AA, for these pages, checked this way, with known\ngaps listed\" can be verified, and it tells the supplier what the work includes before the price is\nset.\n\nThe level is a genuine trade-off. Level AA is the one that public-sector rules and procurement\ndocuments most often name, and nearly any content can reach it. AAA is another matter: the standard\nitself advises against making Level AAA a blanket requirement for whole sites, because some content\ncannot satisfy all of it. Sign-language interpretation of every prerecorded video with sound (1.2.6)\nis one example; a simpler version of any text that needs reading ability beyond lower-secondary\neducation (3.1.5) is another. The workable pattern is AA everywhere, plus the individual AAA\ncriteria that suit the product: 7:1 contrast for long reading text, say, or a stronger focus\nindicator for a tool people drive by keyboard.\n\nThe version has a clear answer. The working group recommends 2.2 as the target even where an\nobligation still names an earlier version, and because 2.2 contains 2.1, building to it costs\nnothing in compatibility. The one wrinkle is 4.1.1: an organisation bound to 2.0 or 2.1 by policy\nmay still have to test and report Parsing.\n\nCost follows timing. Much of AA is settled by early choices: native HTML controls rather than\nhand-built ones, a palette measured for contrast, a visible focus style, layouts that reflow at 320\nCSS pixels. Made at the start, they cost close to nothing. Found by an audit after launch, each\nbecomes a defect repeated on every page that reused the component.\n\n## What it looks like in practice\n\nThis site targets WCAG 2.2 Level AA, and two of its pages describe the work and its limits. The page on\n[taking WCAG 2.2 Level AA across the site](/portfolio/a-site-that-meets-the-accessibility-standard/)\nsets a target covering every page, every language and both colour themes, with conformance to\nbe defended by checks rather than asserted in a document.\n\nIts central instrument is a conformance record with a row for every criterion, each row naming the\nimplementation and checks supporting it. One AAA criterion is taken beyond the target, visual\npresentation in full. Focus appearance is offered rather than claimed, because its contrast over the\nphotograph cannot be proven. The rule engine runs its best-practice rules as well, a difference of\nthirty rules, and one of them failed the moment it was enabled: the brand mark sat outside every\nlandmark on every inner page. A slower check covers thirty-two representative pages in two colour\nschemes and two widths. It proves focus in pixels by pressing the tab key and comparing screenshots,\nwalks each page looking for a keyboard trap, applies the text-spacing overrides and doubles the root\nfont size. At the documented August 2026 three-language stage, the record covered those checks in two themes\nand the stated viewport samples, with one AAA criterion beyond the target and\n1.4.13 recorded as only partly met. Testing with real assistive technology had not\nbeen established. That is evidence of implemented checks and known limits, not\ncomplete Level AA conformance across every configuration.\n\nThe [credits page](/credits/) states the target and a known limitation for a reader. It\nnames 1.4.13 Content on Hover or Focus: the current CSS labels that appear when a\nmark is hovered or focused have no keyboard dismissal control, so that criterion\nis met only in part. The same page lists an axe-core audit of representative\npages across templates and every configured language, against WCAG 2.2 A and AA\nin both colour schemes, inside the quality gate. Those automated rules do not\nestablish complete conformance. W3C's guidance on evaluation tools says human\njudgement is required, which is why the record is kept per criterion rather than\nas a pass mark.\n\n## Where it goes wrong\n\n**The automated audit is green and a keyboard user is stuck in a date picker.** Rule engines read\nwhat the markup says, while much of WCAG is judgement about what the page does: whether alt text\ncarries the point, whether focus order follows reading order, whether a widget can be left with the\nkeyboard. Treat the engine as the floor. Walk every template by keyboard alone, at 200 percent text\nand at 320 CSS pixels wide, and record per criterion who checked it and how.\n\n**A sticky header covers the link that has focus.** 2.4.11 asks that a focused component is not\nentirely hidden by author-created content, and fixed headers, cookie banners and chat buttons are\nthe usual cause. Reserve the space with `scroll-padding-top` set to the header's height, so the\nbrowser scrolls focused elements clear of it, and keep floating panels away from focusable content.\n\n**The sign-in step asks people to remember or retype something.** 3.3.8 rules out a cognitive\nfunction test, such as a password to recall or a puzzle to solve, at any step of authentication\nunless an alternative, a helping mechanism or one of two narrow exceptions applies. A password field\nthat blocks paste, or a CAPTCHA that asks for transcribed text, is where it usually fails. Allow\npaste and password managers, offer a passkey or an emailed link, and prefer object recognition to\ntranscription when a test is unavoidable.\n\n**A statement says \"fully compliant\" and the first audit finds a failure.** A level is met in full\nor not at all, so one missed AA criterion makes the whole claim false. Write the claim the standard\ndescribes instead: its date, the guidelines' title, version and URI, the level, the pages it covers\nand the technologies relied upon. Claim only what every page in scope meets, and name any criterion\nthat falls short by its number, with the reason and the plan, rather than rounding the level up.\n\n## Further reading\n\n- [Web Content Accessibility Guidelines (WCAG) 2.2](https://www.w3.org/TR/WCAG22/) — the\n  normative text: principles, guidelines, success criteria and the conformance requirements.\n- [What's New in WCAG 2.2](https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/) — the\n  nine new criteria one by one, with persona examples, and the removal of 4.1.1 Parsing.\n- [How to Meet WCAG (Quick Reference)](https://www.w3.org/WAI/WCAG22/quickref/) — a customisable\n  list of every criterion with its techniques and documented failures.\n- [Understanding Conformance](https://www.w3.org/WAI/WCAG22/Understanding/conformance.html) —\n  levels, full pages, complete processes and what accessibility supported means.\n- [WCAG 2 Overview](https://www.w3.org/WAI/standards-guidelines/wcag/) — how the versions relate\n  and which supporting documents sit around the standard.\n\n\u003chttps://engineer.company/glossary/wcag/\u003e\n","date_modified":"2026-11-09T21:50:25Z","description":"What WCAG 2.2 asks of a website, how Levels A, AA and AAA differ, what changed since 2.1, and what an honest conformance claim has to contain.","formats":{"gemtext":"https://engineer.company/glossary/wcag/index.gmi","gopher":"https://engineer.company/glossary/wcag/gophermap","html":"https://engineer.company/glossary/wcag/","json":"https://engineer.company/glossary/wcag/index.json","markdown":"https://engineer.company/glossary/wcag/index.md","pdf":"https://engineer.company/glossary/wcag/index.pdf"},"kind":"page","language":"en","title":"What is WCAG 2.2?","url":"https://engineer.company/glossary/wcag/","version":1}