Change on Request

Current:

3.2.5 Change on Request: Changes of context are initiated only by user request or a mechanism is available to turn off such changes. (Level AAA)

Proposed:

@@3.2.5 Change on Request: Changes of context, functionality, settings, route and orientation are initiated only by user request or an easily available mechanism is available to turn off such changes. An easily available mechanism is also available to go to previous context, functionality, settings, route and orientation. Exception: The changes are part of an activity where it is essential (e.g. a game)@@

Suggestion for Priority Level:

AA

Related Glossary

route: Directions and flow such as a GPS route

orientation: perspective or view such as map direction

easily available (or easily available mode or setting): one or more of the follwing is true:

• can be set one time with as a wide a scope as possible (such as using the standards of the OS, From ISO 9241-112 or GPII when available);
• with the option to save or to change the setting, were available interoperably, but also for the scope of the set of web pages;
• is reachable from each screen where it may be needed, and the path and the control conforms to all of this document.

• can be set one time with as wide a scope as possible (such as using the standards of the OS, ETSI or GPII when available); and
• with the option to save or to change the setting, were available interoperably, but also for the scope of the set of Web pages; and
• is reachable from each screen where it may be needed, and the path and the control conforms to all of the document.

What Principle and Guideline the SC falls within.

Principle 3, Guideline 3.2 - Predictable
Update to 3.2.5

Description

Any content, settings or functionality which changes unexpectedly, without user initiation can result in significant barriers for users with cognitive disabilities. Unexpected changes in any of these areas can result in loss of focus, anxiety, or confusion in understanding or using a user interface. Examples include but are not limited to:

• Automatic launching of new windows or pop-ups
• Submission of forms through mechanisms other than a button that is clearly labeled using simple language to submit the form
• Rerouting automatically by a GPS
• Changing the direction of a map in a GPS

For example, a user may not have a sense of direction or know their left and right. Before using a GPS they may study the route so that they know approximately what they are doing and can augment the directions of the GPS with their own context, using the GPS for cues. The GPS automatically reroutes them because of a small traffic delay. They become completely lost and disorientated and can no longer use the application.

Benefits

This Success Criterion give users with cognitive disabilities more control over how Websites and applications behave and display information giving them the opportunity to make choices that enable them to use the content and complete the task.

Initiating changes only when requested by a user is particularly helpful for:

• Focus and attention related disabilities
• Users with weak orientation
• Users with low executive function
• Memory related disabilities
• Users with anxiety disorders

See:

• Distractions issue paper
• Gap analysis
• User needs Tables 2 and 9 as well as tables 4 and 5
• Background research document
• Semantics for adaptive interfaces
• Script for personalization and Example for personalization
• Techniques
• Personalization and Preferences

Related Resources

Resources are for information purposes only, no endorsement implied.

• User research article
• Cognitive Disabilities and the Web: Where Accessibility and Usability Meet? - NCDAE
• Cognitive Disabilities - Design Considerations - WebAIM

Testability

For all content

Step 1: Identify any automatic changes in context, functionality, settings, route and orientation (using a similar way to how we identify changes in context now)

Step 2: Confirm there is an easy way for the user to suppress any changes from step 1

Step 3: Confirm an easy to use mechanism is available to go to the previous context, functionality, settings, route and orientation from Step 1.

Content specific examples

For slide shows, audio or video, confirm that:

• Content does not autoplay or
• A mechanism for stopping or pausing is present

For intermittent content updates such as news feeds or embedded social media updates, confirm that:

• A mechanism for pausing an update is present
• A roll back is present

Techniques

• Providing warning for any of the changes in context and allowing the user to prevent the change if required. The warning allows sufficient time for the user to process the warning and react.
• Providing a "pause" button for sideshows, video and audio
• Providing a "request update" and "pause update" button for news feeds or embedded social media updates
• Setting the autoplay attribute on an embedded YouTube video to "0"
• Using semantics and personalization to control changes
• Allowing a user to turn off reroutes
• Allowing a user to turn off changes in orientation