A Roundup Of WCAG 2.2 Explainers — Smashing Magazine

WCAG 2.2 Is Official: Where To Read Up On The Changes

On October 5, 2023, WCAG 2.2 was formally published as a "W3C Recommended" web standard. The update replaces WCAG 2.1 with an additional nine success criteria, covering fresh ground around focus appearance, dragging movements, and accessible authentication. Notably, WCAG 2.1's criterion 4.1.1 Parsing has been removed entirely.

Anyone who has worked with the guidelines knows that translating success criteria into concrete implementation can be difficult. Fortunately, many accessibility specialists and large organizations have published detailed explainers covering not just what changed, but how to actually conform. Below is a roundup of technically solid resources written or updated around the time of the W3C recommendation, curated without any sponsorship or endorsement bias.

Deep Technical Explanations

Patrick Lauke (TetraLogical) — What's New In WCAG 2.2: A current WCAG working group member and Principal Accessibility Specialist at TetraLogical, Lauke's overview shines by pairing each success criterion with conformance examples. The visuals help illustrate exactly what a compliant focus indicator looks like versus one that fails, making it an essential resource beyond simply listing the changes.

James Edwards (TPGi) — New Success Criteria In WCAG 2.2: Edwards, a seasoned accessibility consultant, goes step-by-step through each new criterion with discussion on how to meet the standard. This guide includes contextual asides explaining why specific changes were drafted and how the working group arrived at its decisions, adding background that most other write-ups lack.

Hidde de Vries — What's New In WCAG 2.2?: A former W3C staffer, de Vries originally published his overview during the draft phase and has since kept it current with post-recommendation revisions.

Practical Guides And Checklists

Dennis Lembrée (Web Axe) — WCAG 2.2 Checklist With Filter And Links: While Lembrée's blog post announcing WCAG 2.2 is brief, the real value lies in his accompanying CodePen demo. The interactive checklist lets you filter success criteria by WCAG release — 2.0, 2.1, or 2.2 — and aligns each entry against the corresponding chapter of the specifications. It correctly lists all WCAG 2.0 criteria as a baseline, which is useful now that 2.2 supersedes them.

Deque Systems — Deque Systems Welcomes and Announces Support for WCAG 2.2: Aside from the corporate announcing, this post's valuable tables outline each new standard along with the specific user groups most affected. If you need a quick at-a-glance overview, this works well; as a guide to actual implementation, look elsewhere in this roundup.

Level Access — WCAG 2.2 AA Summary and Checklist for Website Owners: Despite the title referencing a checklist, the content operates as a high-level overview more than actionable task list. It does offer a downloadable WCAG checklist, but requires exchanging an email address for it.

Large-Scale Government Conformance

GOV.UK — Understanding WCAG 2.2: GOV.UK's Service Manual update remains one of the fairest official government takeaways on WCAG 2.2. It frames the changes not by criterion number but by the accessibility barriers presented, providing concrete examples of defective patterns and corrected alternatives.

The document is also transparent about a measured conformance timeline: GOV.UK will maintain WCAG 2.1 AA compliance in the interim, with a stretch goal toward full WCAG 2.2 AA compliance by October 2024.

Additional Explainers Worth Digging Into

Kate Kalcevich — WCAG 2.2: What Changes for Websites and How Does It Impact Users?: Kalcevich spends less time on strict conformance mechanics and more on the user experience benefits behind the changes. As she writes, "when thinking about accessibility beyond compliance, it becomes clear that the latest W3C guidelines are just variations on a theme. The theme is removing barriers and making access possible for everyone." Don't expect detailed code samples here; this is a qualitative resource emphasizing who the updates help and how.

Chris Pycroft — WCAG 2.2 Is Here: Although announcement-style, it includes a downloadable "WCAG 2.2 Map" PDF. The map spawns from the four core principles (Perceivable, Operable, Understandable, Robust), branching into each success criterion. A useful visual artifact for diagrams and documentation, though it would be more practical if offered as HTML.

Shira Blank and Joshua Stein — After More Than a Year of Delays, It Is Time to Officially Welcome WCAG 2.2: More accessible to business stakeholders than developers, this overview notes that WCAG 2.2 is expected to be the last 2.x version before the WCAG 3 release — reportedly codenamed "Silver." Nice trivia, but stay on top of the technical matters first.

Nathan Schmidt — Demystifying WCAG 2.2: Schmidt's strength, true to the post's name, is removing jargon. Coupled with clean visual diagrams and examples, it's a decent first-stop reading for developers finding the technical language of the W3C spec overwhelming.

Developer Focus And Business Implications

Craig Abbott — WCAG 2.2 And What It Means For You: Writes more conversationally than most, anchored in personal perspective as a developer who regularly handles accessibility audits. Abbott includes some of his own views on the spec, such as on the Focus Appearance criterion: "I personally feel like the new criteria for Focus Appearance could have been braver and removed some of the ambiguity around what is already often an accessibility issue." Not a purely reference resource, but readable when you need a mental refresh before tackling fixes.

Jason Taylor (UsableNet) — WCAG 2.2: Taylor's guide is the most business-oriented of the links here, attempting to translate developer-level success criteria into organizational impacts and responsibilities — think, review this with legal, product, and QA in mind.

There are far more WCAG 2.2 explainers circulating than can be listed in any single roundup. As you'd expect, a large portion of the content between them overlaps — the new success criteria aren't numerous, although WCAG 2.1 dates back five years now. What stands out, then, is the nuance each contributor brings: some focus on user impact, others on compliance mechanics, edge cases, and on-the-ground implementation approaches. Expect even more resources soon; the points below and in the materials above make a reasonable baseline for any organization planning its 2.2 conformance work.

Head to the W3C WCAG 2.2 specification itself for the ultimate source of truth. But this collection should give enough breadth and depth to plan remediation efforts correctly.