Change on Request

About

Version:	WCAG 2.0 and up
Number:	3.2.5
Level:	AAA
Applicability:	Buttons Controls Forms Inputs Links
Requirement:	Changes of context are initiated only by user request or a mechanism is available to turn off such changes.
Guidance:	Understanding Success Criterion 3.2.5 How to meet Success Criterion 3.2.5
Techniques:	G76: Providing a mechanism to request an update of the content instead of updating automatically G110: Using an instant client-side redirect H76: Using meta refresh to create an instant client-side redirect H83: Using the target attribute to open a new window on user request and indicating this in link text SCR24: Using progressive enhancement to open new windows on user request SCR19: Using an onchange event on a select element without causing a change of context

Purpose

The purpose of this success criterion is to ensure that users have full control over any changes of context (new pages opening, focus changing to a new element, content added or removed, redirects).

Automatic changes of context can confuse users, especially if they cannot perceive that a change has occurred.

How to Meet

Instead of automatically triggering changes of context, authors should provide users options to confirm when they want such changes to occur (e.g., indicating in links when a new window will open).

Additional Information

The following knowledge base pages provide more information about how to address this success criterion for publishing content: