Level AAAUnderstandable
3.2.5

Change on Request

The strict version: big changes (new pages, popups, redirects) happen only when the user asks, never automatically.

In plain English

The Level A rules stop specific surprises (focusing or changing a field must not suddenly whisk you elsewhere). This AAA rule broadens that to every big change: opening a new window, redirecting, or heavily rearranging the page should happen only because the user asked, or be switchable off.

Sudden context changes are disorienting for everyone, and genuinely stranding for screen-reader users who may not notice the page changed under them.

Who this is for

  • Screen-reader users, who can be left lost when the context changes unannounced.
  • People with cognitive differences, disoriented by unexpected jumps.

How to check and fix it yourself

Look for anything that changes context on its own: auto-redirects, self-opening popups, links opening new tabs silently. Make them user-initiated and announce new windows.

Auto-redirect after landing.                      ✗ let the user click through
Link opens a new tab, labelled "(opens new tab)". ✓
Popup opens on its own.                            ✗ trigger it on a click

Where we can help

We find automatic context changes across your store and flag the ones that fire without the user asking. Unexpected jumps also raise bounce rates, so fixing them helps engagement too.

How to meet it

Techniques the W3C accepts as sufficient (summarized). Follow a link for the full method.

Frequently asked questions

What does change on request require?+

Success Criterion 3.2.5 (Level AAA) says major changes of context, opening a new window, navigating to a new page, or significantly rearranging content, happen only when the user asks for them, or the user can turn off such automatic changes.

How is this stricter than 3.2.1 and 3.2.2?+

3.2.1 On Focus and 3.2.2 On Input (both Level A) stop specific triggers: focusing or changing a control mustn't cause a surprise context change. 3.2.5 (AAA) generalises that to all automatic context changes, they should be user-initiated or switchable off.

What are common examples on a store?+

Auto-redirects, pop-up windows that open by themselves, carousels that jump you elsewhere, and links that open new tabs without warning. Each should be initiated by the user, and new windows should be announced.

Reference

This is a plain-language explainer. The authoritative source is the W3C Web Content Accessibility Guidelines (WCAG) 2.2.

WCAG 2.2 © W3C. Excerpts are paraphrased; see the linked documents for the normative text.

Not sure if your store passes 3.2.5?

A human auditor checks this and every other criterion against your live store, and documents the result.

Book an audit