Augment

Accessibility Basics: WCAG 2.2 for Product Teams

Accessible design is good design for everyone. These are the practical parts of WCAG 2.2 that product teams can act on today.

A wheelchair accessibility symbol on a concrete wall
Photo by marianne bos on Unsplash, with an Augment halftone treatment
Executive Summary

Key Takeaways

  • WCAG 2.2 became a W3C Recommendation on 5 October 2023 and added nine new success criteria.
  • Target Size (Minimum) at level AA asks for pointer targets of at least 24 by 24 CSS pixels, with exceptions.
  • Cover the basics first: contrast, keyboard use, labels, focus, and clear errors.
  • Build accessibility into design and code from the start. Fixing it later costs more.

Why it matters

The W3C's accessibility principles describe a web that works for people with a wide range of abilities, including vision, hearing, movement, and cognition. Many accessibility improvements also help everyone, such as captions in a noisy room or good contrast in bright sunlight.

What is new in WCAG 2.2

WCAG 2.2 became a W3C Recommendation in October 2023. It adds new success criteria, including a minimum target size, focus visibility improvements, easier alternatives to dragging, and less reliance on memory in sign-in and forms.

AreaNew requirement in plain words
Target sizePointer targets at least 24 by 24 CSS pixels, or enough spacing (AA)
FocusThe focused element is not fully hidden by other content (AA)
DraggingProvide a non-dragging alternative for drag actions (AA)
Consistent helpPut help in the same place across pages (A)
Redundant entryDo not make users re-enter information already given (A)
Accessible authenticationDo not require solving cognitive puzzles to sign in (AA)

The older level AAA criterion still suggests 44 by 44 pixels, which is also a sensible target for touch.

A practical checklist

  • Contrast: text and key UI elements meet the required ratios.
  • Keyboard: everything can be used without a mouse, with a visible focus indicator.
  • Labels: every field has a clear, programmatic label.
  • Alternatives: images have meaningful alt text, and video has captions.
  • Errors: messages identify the problem and how to fix it.
  • Motion: respect reduced-motion settings and avoid flashing content.

Build it into your process

Add accessibility to design reviews and definitions of done. Use automated checks to catch common issues, then test with a keyboard and a screen reader. Automated tools find only a portion of problems, so manual testing matters.

Use patterns that already work

For complex widgets like dialogs, menus, and tabs, follow the W3C's ARIA Authoring Practices Guide. It documents expected keyboard behavior and roles, which saves you from inventing something that breaks assistive technology.

Frequently Asked Questions

Nine new success criteria, covering things like minimum target size, focus visibility, dragging alternatives, and accessible sign-in.

Sources and further reading

  1. Web Content Accessibility Guidelines (WCAG) 2.2W3C · Published · Updated · Accessed
  2. What's New in WCAG 2.2W3C Web Accessibility Initiative · Updated · Accessed
  3. Accessibility PrinciplesW3C Web Accessibility Initiative · Updated · Accessed
  4. ARIA Authoring Practices GuideW3C Web Accessibility Initiative · Undated page · Accessed

Credits

  • Written by Augment Editorial Team, Product design and engineering, Augment Lab.
  • Cover photo Photo by marianne bos on Unsplash, with an Augment halftone treatment, used under the Unsplash License.
  • Research Statistics and standards are cited from the sources above. Always check the original page for the latest version.

Augment Product Design

Ready to make your product clearer?

From first concept to go-live, we turn complex product ideas into clear, useful experiences.

Accessibility Basics: WCAG 2.2 for Product Teams | Augment. Lab