Change on Request
Success Criterion 3.2.5 (Level AAA)
Question
In your website/application, are there functions or controls that will auto-initiate changes in context not specifically requested by the user?
Why is this important
If users don’t have control over or are made aware of context changes on a web page, they could become very confused about what is happening on the page.
Whom does it benefit?
Example 1:
As a person with low vision
I want a submit button on my form rather than having the
form submit automatically when fields are completed
so that I can take extra time to review my entries and
submit the form when I’m sure that all of the information is correct.
Example 2:
As a screen reader user
I want to be notified that clicking on a button or link
will open in a new window
so that I can be aware that the content will be in a new
window and can choose whether or not to open it.
What should you do?
- When possible, avoid automatic changes to context such as launch of new windows, move of focus, submission of forms when fields completed, etc.
- In situations when automatic changes are unavoidable, keep users informed about the changes.
How do you do it?
- Provide clearly labelled user controls to enable context change.
- If something will occur automatically, provide text alerts on what is going to happen and instructions on how to pause or prevent it.
Need technical guidance?
Technical guidance is available for implementing this Success Criterion at
the
Understanding Success Criterion 3.2.5 - Change on Request