A website should support different ways of use.
Automated tools find only some accessibility issues. Keyboard use, screen readers, zoom and content clarity also need manual review.
Structure and meaning
Headings, regions, links and controls receive semantics that match their actual purpose.
Focus and keyboard
Every action must work without a mouse, with visible focus and no traps inside menus, dialogs or forms.
Contrast and motion
Text and controls receive sufficient contrast while reduced motion removes movement that is not needed for comprehension.
Sufficient means at least 4.5:1 for normal text and 3:1 for large text, meaningful icons and control borders. Values are checked in every state: default, hover, focus and error.
What WCAG 2.2 adds
Version 2.2 adds criteria that existing websites often miss:
- a focused element must not be fully hidden behind a sticky header or banner
- touch targets of at least 24 × 24 pixels or with enough spacing
- any dragging action needs a single tap or click alternative
- help and contact options, when repeated across pages, stay in the same place
- a form does not ask again for information already entered in the same process
- sign-in does not rely only on memorising or retyping a code, so pasting a password has to work
Target size and focus are checked on phones too, as part of improving the mobile layout.