3.2.5 – Change on Request (Level AAA)

Don’t change elements on your website until users ask

Some of your users find automatic changes hard to deal with. Unexpected actions can interrupt their concentration and prevent them from reaching their goals. Help your users by keeping them in control and avoiding elements on your website that change automatically.

What to do

To pass this guideline, you need to ensure the following five statements are true:

  1. If you have an element that updates automatically (like a live news ticker), there is an option to pause this and update only when requested; and
  2. All links open in the same window, unless it’s essential (for example, opening a transcript to a video); and
  3. If a link does open in a new window, the user is aware of this (for example, in the anchor text of the link or by an icon); and
  4. Forms do not auto-submit when fields are filled; and
  5. Any redirect from one page to another is immediate.


  • This guideline builds on Guideline 3.2.2 and Guideline 2.2.2 by removing some exceptions, so you may already have passed!
  • The best way to redirect a user from one webpage to another is to do it without them noticing. One of the simplest ways to do this is to edit a website’s .htaccess file, which is in the root directory (not all servers will allow you to edit this file, so check with your hosting provider).

See also

Free Developer Resources

Join over 2,000 accessibility fans and get free developer resources like WCAG 2.0 Checklists and a sample from my book.

Powered by ConvertKit

Over 250 people just like you have learned more about WCAG 2.0 with my guidebook.

Learn more >