Sign inTry Eidren
ComputerYour chores on real websites, doneResearchCited answers to real questionsApps and sitesWorking software from a descriptionDocumentsDecks, documents and spreadsheets, as real filesDataCharts with the story in plain wordsAutomationsThe weekly task, done every week
Watch it workEveryday chores, done on Eidren’s own computer

Use cases/Research

Our web app was audited against WCAG 2.1 AA. Which success criteria are new in WCAG 2.2, and which of them do we have to meet at level AA? Use the W3C pages and cite each one.

WCAG 2.2 adds nine new success criteria since WCAG 2.11. Four are Level AA, so you have to meet them: 2.4.11, 2.5.7, 2.5.8 and 3.3.82. Two more, 3.2.6 and 3.3.7, are Level A, which an AA claim also covers2.

Success criterionLevel
2.4.11 Focus Not Obscured (Minimum)AA
2.4.12 Focus Not Obscured (Enhanced)AAA
2.4.13 Focus AppearanceAAA
2.5.7 Dragging MovementsAA
2.5.8 Target Size (Minimum)AA
3.2.6 Consistent HelpA
3.3.7 Redundant EntryA
3.3.8 Accessible Authentication (Minimum)AA
3.3.9 Accessible Authentication (Enhanced)AAA

What the four AA additions require

  • 2.4.11 Focus Not Obscured: a component with keyboard focus must not be entirely hidden by content you added, such as a sticky footer2
  • 2.5.7 Dragging Movements: anything that needs dragging must also work with a single pointer without dragging2
  • 2.5.8 Target Size: pointer targets must be at least 24 by 24 CSS pixels, or meet the spacing exceptions2
  • 3.3.8 Accessible Authentication: signing in must not depend on a cognitive function test unless an alternative is offered2
Read
The W3C specification and its summary of changes
Cited
Every criterion
NextWe’re moving our wiki. Which Markdown features will survive?

What will you hand off first?

Start with the task you have been putting off.