a11y teacher edition W3C WCAG 2.2 & WCAG 3.0 draft reference
codea11y.dev
Plain English Accessibility Hub

Translating W3C Standards for Designers, Developers, QA & Product teams

Audit Calculator W3C Official

Why WCAG 2.2 Conformance Leaves a Cognitive Usability Gap

WCAG 2.x was constructed around mechanically testable, binary pass/fail success criteria. This model works well for sensory and motor accommodations—measuring contrast ratios (4.5:1), ensuring every button has an accessible name, or verifying full keyboard operability.

However, cognitive and learning disabilities—including ADHD, autism, dyslexia, dyscalculia, traumatic brain injury, memory loss, and early dementia—cannot be fully evaluated by automated scanners. A web page can achieve 100% on automated accessibility audits and pass WCAG 2.2 AA, yet remain completely unusable if:

  • It bombards users with sudden pop-ups and auto-advancing banners mid-task.
  • It hides critical navigation behind cryptic, unlabeled icons.
  • It clears an entire 15-field form because one field had an invalid phone format.
  • It forces users to solve math puzzles or transcribe distorted text to authenticate.
  • It uses dense corporate jargon, double negatives, and ambiguous metaphors.

The W3C published "Making Content Usable for People with Cognitive and Learning Disabilities" (a formal W3C Group Note) to bridge this exact gap. It provides 8 overarching design objectives with practical, tested user experience patterns.

💡 Quick Summary

The 8 Objectives at a Glance

  1. 1. Help users find what they need
  2. 2. Use clear & understandable content
  3. 3. Help users avoid errors & recover
  4. 4. Help users focus & maintain attention
  5. 5. Eliminate memory & calculation demands
  6. 6. Provide support & contextual help
  7. 7. Adapt to user preferences & tools
  8. 8. Test with real neurodivergent users
Read Official W3C Group Note ↗

The 8 Core Objectives Broken Down

Practical UI patterns, common pitfalls, and WCAG mapping for each cognitive objective.

Objective 1

Help users find what they need

User Barrier: Memory loss, executive functioning challenges, or tunnel vision can make it difficult or impossible to maintain mental maps of deep or shifting navigation structures.

Consistent visual layout & navigation

Keep headers, main navigation bars, search bars, and footer utilities in the exact same location across all pages.

Do:

Persistent top-level navigation with active state clearly marked.

Don't:

Navigation menus that shift order, collapse unexpectedly, or disappear on certain sub-pages.

Visible, persistent search on every screen

Provide an always-visible search input with auto-complete and spell-check tolerance for common misspellings.

Do:

Standard search box with visible magnifying glass and clear submit button.

Don't:

Hiding search behind an unmarked hamburger or generic icon on desktop layouts.

Clear hierarchical headings & landmarks

Use logical H1–H6 hierarchy and HTML5 landmark regions (<header>, <nav>, <main>, <aside>, <footer>) so users and assistive tools can easily skim.

Do:

Descriptive headings that clearly preview the section content below them.

Don't:

Vague headings like 'More Information' or skipping heading levels (e.g., H1 directly to H4).

Standard Alignment: Maps to WCAG 2.2: 2.4.5 Multiple Ways, 2.4.6 Headings & Labels, 3.2.3 Consistent Navigation
Objective 2

Use clear and understandable content

User Barrier: Individuals with language processing challenges, dyslexia, or non-native fluency struggle with complex vocabulary, double negatives, idioms, and cryptic symbols.

Plain language & high-frequency vocabulary

Write in short, direct sentences (< 25 words) using the 1,500 most common words corpus. Avoid double negatives and passive voice.

Do:

'Submit your expense claim.'

Don't:

'Submit remuneration documentation pursuant to statutory bylaws.'

Explain jargon, acronyms & non-literal language

Provide clear definitions or expandable glossaries for industry terms, acronyms, metaphors, and idioms.

Do:

'Log in with your SSN (Social Security Number, a 9-digit number issued by the US government).'

Don't:

Using idioms like 'hit the ground running' or unexplained acronyms in instructions.

Pair icons with visible text labels

Never rely on standalone, ambiguous icons for critical actions. Always pair icons with visible, persistent text.

Do:

A floppy disk or checkmark accompanied by the visible text 'Save'.

Don't:

A toolbar of 12 icon-only buttons with no visible labels until hovered.

Standard Alignment: Maps to WCAG 2.2: 3.1.1 Language of Page, 3.1.2 Language of Parts, 3.1.4 Abbreviations; WCAG 3: clear-language
Objective 3

Help users avoid errors and recover easily

User Barrier: Users with dyscalculia, anxiety, or attention impairments make frequent input errors and can become overwhelmed if an entire form is cleared or error feedback is vague.

Visible inline instructions & formatting cues

Provide explicit format examples (e.g. MM/DD/YYYY) directly above or below the input, never relying solely on disappearing placeholder text.

Do:

An input with an explicit helper text: 'Date format: MM/DD/YYYY (e.g. 05/14/1990)'.

Don't:

A light grey placeholder that vanishes as soon as the user starts typing.

Actionable, human error messages

Tell the user specifically what went wrong and exactly how to fix it in plain language. Link the error summary directly to the field.

Do:

'Please enter your 10-digit phone number without dashes or spaces.'

Don't:

'Error: Invalid string format (code 0x482)'.

Reversible actions & undo mechanisms

Allow users to undo actions, review orders before confirmation, and easily recover from accidental clicks.

Do:

A 10-second 'Undo Delete' banner or a pre-submission review step.

Don't:

Immediate permanent deletion with no confirmation or undo option.

Standard Alignment: Maps to WCAG 2.2: 3.3.1 Error Identification, 3.3.2 Labels or Instructions, 3.3.3 Error Suggestion, 3.3.4 Error Prevention
Objective 4

Help users focus and maintain attention

User Barrier: Users with ADHD, autism, or post-concussion syndrome lose focus easily when pages flash, animate automatically, pop up modal interruptions, or crowd content.

Chunk content into manageable steps

Break long multi-field processes into small, logical steps with a visual progress indicator that shows current position.

Do:

A 4-step wizard: 'Step 2 of 4: Shipping Address' with previous/next controls.

Don't:

A single scrolling page with 45 form fields and no visual landmarks.

No unsolicited pop-ups or distractions mid-task

Do not trigger survey pop-ups, newsletter overlays, or promotional modal dialogs while a user is actively engaged in a workflow.

Do:

Suppress promotional banners and feedback prompts during checkout or form completion.

Don't:

Displaying a modal 'Join our newsletter for 10% off' right as the user types their credit card number.

Pause, stop, or hide moving content

Provide obvious pause/stop controls for any carousel, ticker, or background video, and respect CSS prefers-reduced-motion.

Do:

A prominent 'Pause animations' button and honoring system reduced-motion preferences.

Don't:

An auto-advancing carousel that cannot be paused and loops every 3 seconds.

Standard Alignment: Maps to WCAG 2.2: 2.2.2 Pause, Stop, Hide, 2.3.3 Animation from Interactions
Objective 5

Do not rely on memory or mental calculations

User Barrier: Users with short-term memory deficits, executive dysfunction, or dyscalculia cannot memorize codes across tabs, solve math puzzles, or transcribe distorted text.

Accessible authentication (No cognitive tests)

Allow password managers, copy-paste into password and 2FA fields, WebAuthn/Passkeys, or email magic links instead of CAPTCHAs or memory puzzles.

Do:

One-click passkey login or pasting a 6-digit verification code from clipboard.

Don't:

Blocking paste into the password input or requiring users to solve a math problem to log in.

Autofill & eliminate redundant entry

Automatically populate information previously entered in the same session (e.g. shipping address matching billing address).

Do:

Checkbox: 'Billing address matches shipping address' that pre-fills all data.

Don't:

Requiring users to type the exact same street address three times in the same checkout.

Persistent summaries of active context

Keep key details (items in cart, selected flight times, current balance) visible throughout multi-screen flows.

Do:

A sticky or persistent sidebar showing the chosen date and price during reservation steps.

Don't:

Forcing users to click 'Back' three times just to verify what date they selected.

Standard Alignment: Maps to WCAG 2.2: 3.3.7 Redundant Entry (New in 2.2), 3.3.8 Accessible Authentication (New in 2.2)
Objective 6

Provide support and help when needed

User Barrier: When users get stuck, confused, or frustrated, finding help must be instant, predictable, and stress-free.

Consistent help in the same location

Place contact details, live chat, or help links in the exact same visual and DOM location across every view in a set of web pages.

Do:

A 'Help & Support' button anchored in the top-right header across every single page.

Don't:

Moving the help button to the footer on page 1, the sidebar on page 2, and omitting it on page 3.

Multiple ways to get assistance

Provide a variety of support mechanisms: human phone number, email, real-time chat, FAQ, and contextual tooltips.

Do:

Offering both self-serve FAQs and a human contact phone/chat option.

Don't:

An automated chatbot loop with no way to speak to a real human or file a written ticket.

Contextual inline help that preserves state

Allow users to open contextual tips or definitions without navigating away or losing their input in an active form.

Do:

An expandable details accordion or non-modal popover that leaves form entries intact.

Don't:

A help link that navigates the browser away to a new page, discarding all form entries.

Standard Alignment: Maps to WCAG 2.2: 3.2.6 Consistent Help (New in 2.2); WCAG 3: consistent-help-available, conversational-support-available
Objective 7

Adapt to user preferences and technologies

User Barrier: Many users with cognitive disabilities rely on personal assistive software—reading rulers, text-to-speech readers, custom fonts, high-contrast colors, or zoom.

Support zoom up to 400% without loss of content

Ensure content reflows into a single column at high zoom levels without horizontal scrolling or overlapping text boxes.

Do:

Responsive flexbox/grid layout that stacks gracefully at 400% zoom.

Don't:

Fixed width containers with overflow: hidden that clip sentences in half.

Allow custom typography & user stylesheets

Do not block user-installed fonts (such as OpenDyslexic or Lexend) or disable text selection.

Do:

Clean semantic HTML allowing reader modes and custom font extensions to operate.

Don't:

Setting user-select: none on article text or overriding user font settings with !important.

Respect OS preferences (Motion & Color)

Support prefers-reduced-motion, prefers-color-scheme (dark/light), and forced-colors mode.

Do:

Honoring the user's high-contrast theme and disabling smooth scrolls when reduced motion is on.

Don't:

Hardcoding white backgrounds with unchangeable low-contrast grey text.

Standard Alignment: Maps to WCAG 2.2: 1.4.4 Resize Text, 1.4.10 Reflow, 1.4.12 Text Spacing; WCAG 3: user-preferences-respected
Objective 8

Test with real users with cognitive disabilities

User Barrier: Automated accessibility scanners (like Axe or Lighthouse) can only test technical syntax (e.g. alt text or ARIA roles). They cannot evaluate clarity, confusion, or cognitive fatigue.

Include neurodivergent participants in user testing

Conduct moderated and unmoderated usability sessions with individuals who have ADHD, autism, dyslexia, aphasia, or memory conditions.

Do:

Testing core checkout and onboarding flows with diverse participants as part of each major release.

Don't:

Declaring a site '100% accessible' solely based on automated CI/CD test passes.

Evaluate cognitive load & task completion time

Measure not just whether a task is technically possible, but how much time, mental effort, and confusion it causes.

Do:

Recording user friction points and measuring ease-of-use scores alongside pass/fail stats.

Don't:

Treating a user who spent 20 minutes struggling with a captcha as a 'successful completion'.

Document usability findings into assertions

Keep records of test findings, feedback, and remediation actions. This directly matches WCAG 3's emerging assertion framework.

Do:

Maintaining an ongoing accessibility support record detailing user testing cohorts and outcomes.

Don't:

Discarding user test feedback as 'subjective preferences' rather than accessibility requirements.

Standard Alignment: Directly drives WCAG 3.0 Assertions (User Testing with People with Disabilities)

How COGA Bridges WCAG 2.2 into WCAG 3.0

📘

What Made It into WCAG 2.2

After years of advocacy from COGA, WCAG 2.2 introduced three breakthrough Success Criteria directly addressing cognitive friction:

  • 3.2.6 Consistent Help (Level A): Requires help features (chat, contact details, FAQs) to appear in the exact same relative order and location across all pages.
  • 3.3.7 Redundant Entry (Level A): Forbids forcing users to re-enter information previously provided in the same session (e.g. shipping address matching billing).
  • 3.3.8 Accessible Authentication (Level AA): Prohibits relying on cognitive function tests (solving math equations, memorizing passwords across tabs, or transcribing CAPTCHAs) without an accessible alternative.
✨

How COGA Shapes WCAG 3.0

WCAG 3 replaces binary A/AA/AAA levels with a flexible architecture that accommodates cognitive needs far better:

  • Assertions over pure automation: WCAG 3 introduces formal "Assertions"—documented organizational proof that teams conducted usability testing with neurodivergent users and adhered to plain language guidelines.
  • Expanded Core Provisions: Provisions like consistent-help-available, cognitive-test-alternatives-available, and trigger-warning-available elevate COGA patterns directly into the normative baseline.
  • Harm & Risk Tagging: WCAG 3 tags failures by their real-world user impact (e.g., stopping a user from completing a critical task or causing financial/privacy risk).
Cutting Edge

2026 Cognitive Accessibility Research Modules

Published by W3C in February 2026, these five modules preview where web accessibility is heading beyond traditional websites.

Draft Note Feb 2026

Voice Systems & Conversational Interfaces ↗

Explores cognitive barriers with voice assistants (Siri, Alexa, interactive voice response). Focuses on giving users enough time to respond, handling pauses without timing out, providing multi-modal visual fallbacks, and supporting plain-language verbal commands.

Draft Note Feb 2026

Technology-Assisted Indoor Navigation & Wayfinding ↗

Addresses sensory overload, disorientation, and memory challenges in indoor spaces (airports, hospitals, transit hubs). Recommends landmark-based turn-by-turn guidance, visual step previews, and simple decision points.

Draft Note Feb 2026

Online Safety & Wellbeing (Algorithms & Data) ↗

Focuses on manipulative UX design (dark patterns), algorithmic rabbit holes, and financial/privacy exploitation. Recommends default safety guards, clear cooling-off periods for transactions, and transparent algorithm explanations.

Draft Note Feb 2026

Supported Decision-Making Online ↗

Enables individuals with cognitive disabilities to grant trusted supporters (advocates, family members) co-browsing, approval, or review permissions without surrendering their passwords or personal autonomy.

Task Force Priority In Drafting

Upcoming 2026 Modules: Trigger Warnings, AI Safety, User Testing ↗

Three high-priority modules scheduled for 2026: clear content warnings for traumatic/triggering material, safety guidelines for AI agents, and a standardized methodology for cognitive usability testing.

Team Action Checklist: Building for Cognitive Accessibility

🎨 Designers

  • Keep persistent, visible navigation and search bars in consistent layout coordinates.
  • Pair all icon buttons with visible text labels; do not rely on hover tooltips alone.
  • Provide generous whitespace, clear margins, and chunk multi-field forms into sequential steps.
  • Avoid auto-advancing carousels and background video loops; design clear pause controls.

💻 Developers

  • Allow clipboard paste on all password, PIN, and two-factor authentication inputs.
  • Support browser autocomplete tokens (autocomplete="email", "tel", etc.).
  • Ensure inline error messages are tied programmatically to fields using aria-describedby.
  • Never clear form state on validation errors; preserve all valid user inputs.

✍️ Content Writers

  • Keep sentences under 25 words and write in active voice using familiar, common words.
  • Avoid double negatives (use "Allow notifications" instead of "Don't prevent notifications").
  • Explain acronyms and technical jargon on first mention with an inline definition.
  • Provide step-by-step instructions with clear bullet points rather than dense paragraphs.

🧪 QA & Researchers

  • Test forms without typing: verify that paste, password managers, and autofill work smoothly.
  • Test with simulated cognitive fatigue: verify recovery steps and clarity of error messages.
  • Conduct usability sessions with participants who have ADHD, dyslexia, and memory impairments.
  • Document cognitive usability findings to prepare for WCAG 3 user testing assertions.