
WCAG Guidelines Explained With Examples for Designers (WCAG 2.2)

Key Takeaways
Design to WCAG 2.2 Level AA today: it rests on four principles and 13 guidelines, and WCAG 3.0 is still a Working Draft.
- A page conforms to Level AA when it meets every Level A and Level AA success criterion.
- WCAG 2.2 added nine success criteria and removed 4.1.1 Parsing. Six of the new ones are Level A or AA and belong in any AA design review.
- Normal text needs a 4.5:1 contrast ratio and large text 3:1. Icons, input borders and focus indicators need 3:1 against adjacent colors.
- Pointer targets should be at least 24 by 24 CSS pixels.
- Automated scanners such as axe, WAVE and Lighthouse find only part of the problem, so conformance also needs manual testing with a keyboard and a screen reader.
- Four WCAG 2.2 additions help people with cognitive disabilities, according to the W3C.
Run the nine-step checklist on the highest-traffic flow first, then add the six new criteria to design reviews.
Most design teams know the WCAG guidelines are the standard for accessible products. The specification is harder to use. It is written for conformance testing, and a designer preparing for a review needs to know what each rule means for a button, a form or a video. This guide translates WCAG 2.2, the current version, into design terms.
It covers the four principles and all 13 guidelines, each with an example and a way to check it. It also explains what Level AA asks for, how WCAG helps people with cognitive and mental-health conditions, why accessibility matters to the business, and where to start on an existing site.
What are the WCAG guidelines?
The Web Content Accessibility Guidelines (WCAG) are the W3C's standard for making web content usable by people with disabilities. WCAG 2.2 became a W3C Recommendation on 5 October 2023, and the current edition is dated 12 December 2024. Four principles sit at the top. Under them are 13 guidelines, and each guideline holds testable success criteria rated Level A, AA or AAA.
Designers usually remember the principles by the acronym POUR.
| Principle | What it asks | Guidelines | A quick design check |
|---|---|---|---|
| Perceivable | People can see or hear the content in some form | Text alternatives, Time-based media, Adaptable, Distinguishable | Meaningful images have alt text; body text meets 4.5:1 contrast |
| Operable | People can use every control with the input they have | Keyboard accessible, Enough time, Seizures and physical reactions, Navigable, Input modalities | Tab through the page; every control is reachable and visibly focused |
| Understandable | People can follow the content and predict the interface | Readable, Predictable, Input assistance | Form errors explain the problem in text |
| Robust | Content works with browsers and assistive technology | Compatible | Custom controls expose a name and role to screen readers |
WCAG 3.0 is still a Working Draft. The W3C says WCAG 3 is not expected to be a completed standard for a few more years, and states that WCAG 2 will not be deprecated for several years after WCAG 3 is finalized. Design against WCAG 2.2 today.
What are WCAG 2.2 AA requirements?
A page conforms to Level AA when it meets every Level A and every Level AA success criterion. Level A is the minimum. AA is the target most product teams and audits work to, and AAA is the strictest level. The W3C advises against requiring AAA for entire sites because some content cannot meet every AAA criterion.
WCAG 2.2 added nine success criteria and removed one, 4.1.1 Parsing. Six of the new criteria are Level A or AA, so they belong in any AA design review:
- Focus Not Obscured (Minimum), 2.4.11. A sticky header or cookie banner must not completely hide the element that has keyboard focus.
- Dragging Movements, 2.5.7. Anything done by dragging, such as moving a card on a kanban board, also works with a single pointer and no drag.
- Target Size (Minimum), 2.5.8. Pointer targets are at least 24 by 24 CSS pixels, with exceptions such as enough spacing or links inside a sentence.
- Consistent Help, 3.2.6. Help options repeated across pages, like a contact link or chat, appear in the same relative order.
- Redundant Entry, 3.3.7. Information a user already gave in the same process is filled in for them or offered for selection.
- Accessible Authentication (Minimum), 3.3.8. Login does not depend on a cognitive function test, such as remembering a password or solving a puzzle, unless an alternative or a mechanism to assist is available.
Perceivable guidelines with design examples
Perceivable guidelines make sure no information depends on a single sense.
Text alternatives (1.1)
Every image or icon that carries meaning needs a text equivalent. A photo of a cat with its face in a slice of pizza gets alt text that says exactly that. Purely decorative images are marked so screen readers skip them.
The common failure is alt text that repeats a file name like "IMG_2041". Check it with a screen reader.
Time-based media (1.2)
Audio and video need an equivalent for people who cannot hear or see them. Captions cover dialogue and the sounds that matter, such as a door slamming or music starting. Audio description narrates on-screen action the soundtrack does not explain, and the quickest way to find the gaps is to watch a clip with your eyes closed.
Transcripts help both groups and anyone who prefers reading. Otter.ai and similar tools transcribe uploaded audio and video automatically. Our view is that the output still needs a human pass for names and technical terms.
Adaptable (1.3)
Adaptable content keeps its meaning when the layout changes. On a phone, the desktop menu collapses behind a menu button, and the page works in portrait and landscape. Correct headings, lists, form labels and table headers in the code let screen readers and reader modes rebuild the structure.
Two related AA checks follow. Text must resize to 200 percent without losing content or functions, and the layout must reflow at a width of 320 CSS pixels without scrolling in two directions.
Distinguishable (1.4)
Distinguishable content stands out from its background. At Level AA, normal text needs a contrast ratio of at least 4.5:1 and large text at least 3:1, while icons, input borders and focus indicators need 3:1 against adjacent colors. Black on white passes easily. Light grey placeholder text on white usually fails.
Level AAA raises normal text to 7:1 and asks that background audio sit at least 20 decibels below speech. Color alone should never carry the message, which means an error field needs text or an icon as well as a red border. WebAIM's Contrast Checker tests any color pair against both levels, and our guide on developing for colorblind users goes deeper into color choices.
Operable guidelines with design examples
Operable guidelines make every control usable with the input a person actually has.
Keyboard accessible (2.1)
Everything a mouse can do, a keyboard must do too. An accordion button should take focus with Tab and open with Enter or Space.
Links and buttons are different elements: a link takes the user to a page, and a button performs an action, such as submitting a form or opening a menu. Screen readers announce them differently, so the wrong element confuses people who rely on those announcements. To check, put the mouse away and Tab through the page.
Enough time (2.2)
People get enough time to read and act. A carousel or background video that starts on its own and runs longer than five seconds needs a way to pause, stop or hide it. Time limits must be adjustable, and one accepted pattern warns the user and gives at least 20 seconds to extend with a simple action. A banking site that asks "Stay signed in?" before logging out an inactive user follows that pattern.
Seizures and physical reactions (2.3)
Content must not flash more than three times in any one-second period, unless the flashes stay below defined thresholds. The simplest design rule is to leave strobe effects out of animations, video intros and loading states.
Navigable (2.4)
People should always know where they are. Breadcrumbs show the path to the current page, the active menu item looks different from the rest, and each page title describes its page. Focus order should follow the visual order. The new Focus Not Obscured criterion fails when a sticky footer covers the focused link.
Input modalities (2.5)
Input modalities cover touch, pointer, voice and other inputs beyond the keyboard. Someone with limited mobility may use a touch screen, and someone else may control the page by voice. Targets need to be at least 24 by 24 CSS pixels or spaced well apart. Drag-only interactions need a click or tap alternative.
Understandable guidelines with design examples
Understandable guidelines make the wording, page behavior, forms and error messages easy to follow.
Readable (3.1)
Readable content uses plain words and tells software which language it is in. Every page needs a lang attribute on its html element. A phrase in another language gets its own lang attribute on a span, so screen readers pronounce it correctly.
Explain jargon and abbreviations in the text. Writing "National Aeronautics and Space Administration (NASA)" on first use works for every reader, including touch users who never see a hover tooltip.
Predictable (3.2)
Pages that look alike should behave alike. Keep the main menu, search and help in the same place on every page. A field receiving focus should never change the page on its own. A dropdown that submits a form the moment someone picks an option breaks that expectation.
Input assistance (3.3)
Forms should help people avoid mistakes and fix them. Each field has a visible label and a format hint, such as "Expiry date (MM/YY)". When an error happens, describe it in text next to the field ("Enter the date as MM/YY"). WCAG 2.2 adds two related rules: do not ask for the same information twice in one process, and do not make login depend on memory or puzzles.
What does the Robust principle require?
Robust, the fourth principle, asks that content work with current and future browsers and assistive technologies. Its single guideline, Compatible (4.1), centers on Name, Role, Value. Every user interface component must expose its name and role to assistive technology, and its states and values must be readable and settable in code.
A custom toggle built from a div has to announce itself as a switch and report whether it is on. Native HTML elements give this behavior by default, which is why semantic HTML is usually the cheapest fix. WCAG 2.2 dropped 4.1.1 Parsing as obsolete.
How do WCAG guidelines support users with cognitive and mental-health conditions?
WCAG supports these users mainly by lowering memory load, time pressure and surprise. The W3C describes four of the WCAG 2.2 additions as helping people with cognitive disabilities: Consistent Help, Redundant Entry, and both Accessible Authentication criteria. Our view is that older guidelines matter just as much to someone managing anxiety, ADHD or depression:
- Enough time removes countdowns that force a rushed decision.
- Predictable keeps the layout stable, so a person does not have to relearn the interface on a hard day.
- Input assistance gives clear labels, examples and errors that explain how to recover.
- Pause, stop or hide controls let people silence auto-playing media and animation.
- Readable pushes plain words and explained terms.
In a teletherapy or mood-tracking app, these rules translate into short screens with one task each, saved progress, a help link in the same spot on every screen, and settings for text size and color. These are design guidelines and make no clinical claim. Treat WCAG as the minimum, and test with people who live with these conditions.
Why does accessibility matter for business?
Accessibility widens the market a product can serve and lowers legal risk. The World Health Organization's disability fact sheet (2023) estimates that 1.3 billion people, about 16% of the global population, experience significant disability. A checkout that only works with a mouse turns away keyboard and screen reader users within that group, along with anyone using a phone with one hand.
Regulation adds pressure. Arbisoft's accessibility team works with the ADA and Section 508 in the US and the European Accessibility Act and EN 301 549 in the EU, and the obligations differ by market and sector, so confirm with legal counsel which ones apply to your product. Accessible design also tends to help everyone. High-contrast text is easier to read in sunlight, and captions help people watching in a noisy place.
How do you make a website more accessible?
Start with the checks that catch the most common barriers, then move to a full audit. This order works well for an existing site:
- Tab through your key pages with no mouse. Every control should be reachable and show a visible focus ring.
- Use semantic HTML elements such as header, nav, main, button and form in place of generic div and span elements.
- Review alt text on every meaningful image, and mark decorative images so screen readers skip them.
- Rewrite vague link text. "Read our accessibility testing guide" tells a screen reader user far more than "Learn more".
- Test contrast for text, icons and input borders.
- Give every form field a visible label tied to its input in code, with format hints such as "Date of birth (DD/MM/YYYY)" and errors written in text.
- Add captions and transcripts to video and audio.
- Zoom to 200 percent and narrow the window to 320 CSS pixels to confirm nothing is cut off.
- Run scanners such as axe, WAVE or Lighthouse, then test with a screen reader such as NVDA on Windows or VoiceOver on Mac.
Automated scanners find only part of the problem; they cannot judge whether alt text is meaningful or a checkout makes sense when read aloud. Our article on accessibility testing methods and tools covers the full testing process.
How Arbisoft audits a product against WCAG 2.2 AA
Arbisoft's accessibility audits combine automated scanning with manual review against WCAG 2.2 Level AA, or a higher level when a client needs it. A rapid sample audit covers up to three high-priority pages or user flows. Findings are logged with severity, user impact and expected versus actual behavior, then ranked by user impact and compliance risk before the team works with designers and developers on fixes.
Retesting confirms each fix, and a final VPAT or Accessibility Conformance Report (ACR) records conformance after remediation. The team names date pickers, charts, videos, interactive tables and content that updates without a page reload as frequent trouble spots. Those components deserve extra time in design review. Quick add-on scripts do not fix them, as our post on why accessibility overlays fail explains.
Frequently asked questions
Does meeting WCAG 2.2 AA also cover WCAG 2.1 AA?
In practice, yes. WCAG 2.2 keeps the WCAG 2.1 success criteria and adds nine new ones. The one change in the other direction is 4.1.1 Parsing, which WCAG 2.2 removed as obsolete.
Should we wait for WCAG 3.0 before fixing accessibility?
Waiting is unnecessary, because WCAG 3.0 is an incomplete Working Draft and the W3C expects it to take a few more years to finish. WCAG 2 will stay in use for several years after that.
Can automated tools prove a site meets the WCAG guidelines?
Automated tools cannot prove conformance on their own. Scanners such as axe, WAVE and Lighthouse catch problems like missing alt text, missing form labels and low contrast quickly. They cannot tell whether alt text describes the image well, whether focus moves sensibly through a modal, or whether a flow makes sense to a screen reader user. Conformance needs manual testing with a keyboard and assistive technology as well.
What contrast ratio do buttons and icons need?
Icons, input borders and other visual parts of controls need at least 3:1 against adjacent colors at Level AA. Text on a button follows the text rules, so it needs 4.5:1, or 3:1 if it is large.
Getting WCAG 2.2 AA into your design process
For a team starting to apply the WCAG guidelines, run the nine-step checklist on the highest-traffic flow, such as sign-up or checkout, and fix what it finds before the next release. Then add the six WCAG 2.2 Level A and AA additions to your design review template, so new screens meet AA from the first draft.
Products facing a procurement deadline or a regulated market need more than a checklist. A formal audit gives a prioritized issue list and conformance documentation buyers can review. Arbisoft's accessibility audit and remediation services test web apps, mobile apps and documents against WCAG 2.2 AA, with options that include a rapid sample of key flows and a full audit ending in a VPAT.
...Loading Related Blogs









