Back
NoteOct ’232 min read

WCAG 2.2 is about not repeating yourself

WCAG 2.2 became a W3C Recommendation this month with nine new success criteria. Read together, several of them ask the same thing: don’t make people do work twice, or remember what the product could remember for them.

Typeface

On October 5, WCAG 2.2 became a W3C Recommendation. It adds nine new success criteria and retires one, 4.1.1 Parsing. Adrian Roselli notes that it arrived about a year late.

It’s easy to read the list as nine more boxes to tick. Read together, it says something more useful. Several of the new criteria ask the same thing: don’t make people do work twice, or remember what the product could remember for them.

  • 3.3.7 Redundant Entry (A): If someone already entered information in a process, fill it in or let them pick it, rather than asking again.
  • 3.3.8 Accessible Authentication (AA): Signing in shouldn’t depend on a cognitive test like recalling a password or solving a puzzle, unless there’s another way through, such as a password manager or copy and paste.
  • 2.5.8 Target Size (AA): Targets need a minimum size, or enough space around them.
  • 2.5.7 Dragging Movements (AA): Anything you can do by dragging needs a way to do it with a single pointer and no drag.
  • 2.4.11 Focus Not Obscured (AA): When something has keyboard focus, sticky headers and banners can’t cover it completely.

None of these is exotic. They describe a product that respects effort. A person with a memory impairment benefits most, and so does everyone filling in a form on a phone in a hurry.

These are the rules I’d expect professional tools to break most. Dense software loves sticky headers, small targets and drag to reorder, because experts use it all day and the screen is full.

I’ve designed a lot of dense software, and I’ve built a deliberate repeat into some of it. On Uber’s experimentation platform, rolling back a flag asks you to type the flag’s name. That slows down the one person who is in a hurry, on purpose, because a rollback changes what hundreds of thousands of people see. The criterion allows for re-entry that’s essential or there for security, and I’d defend that one under it.

The test I’d take from 2.2 is simpler than the spec. For every place your product asks someone to repeat themselves, ask whether the repeat protects them. If it does, keep it. If it only protects your schema, remove it.