3.2 Understandable > Predictable Flashcards
What’s inside 3.2, Predictable?
- 2.1 On Focus - A
- 2.2 On Input - A
- 2.3 Consistent Navigation - AA
- 2.4 Consistent Identification- AA
- 2.5 Change on Request - AAA
3.2.1 Understandable > Predictable > On Focus
A
What?
When any user interface component receives focus, it does not initiate a change of context. (A change of content is not always a change of context. This success criterion is automatically met if changes in content are not also changes of context.)
How? Use activate rather than focus for context change.
It is recommended that when links are opened to a new window, there is advance warning.
3.2.1 On Focus — new windows and tabs
Don’t change context on focus-
Limit the use of links or buttons that open new windows or tabs within Web content. In general, it is better not to open new windows and tabs since they can be disorienting for people.
From an accessibility standpoint it IS preferable to open new windows outside of the current page when 1) opening it within the page interrupts the flow of filling out a form, or 2) the user is in a logged in secure area and the opened window would terminate the login.
3.2.1 On Focus– what is the failure for this one?
Using a script to remove the focus from a focused on element. This removes both the focus indicator AND the focus itself.
Looks something like this-
3.2.2 Understandable > Predictable > On Input
A
What? Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. entering data or selecting a form control has predictable effects, activating a form control changes it (checkbox) but a link or button does not.
How? Provide Submit button, say that a change in context will occur upon activation, use an onchange event that does not change context
Failures- Autosubmitting a form, new window without warning if radio button, checkbox or select list changes
3.2.3 Consistent Navigation
AA
What? Use of consistent presentation and layout for users who interact with repeated content within a set of Web pages and need to locate specific information or functionality more than once.
How? G61: Presenting repeated components in the same relative order each time they appear
Advisory: running headers and footers and page numbers in PDFs.
Failure: presenting them in different order
3.2.4 Consistent Identification
AA
What? Consistent identification of functional components that appear repeatedly within a set of Web pages. Consistent does not mean identical.
How? G197: Using labels, names, and text alternatives consistently for content that has the same functionality AND following the sufficient techniques for Success Criterion 1.1.1 and sufficient techniques for Success Criterion 4.1.2 for providing labels, names, and text alternatives.
Failure- F31: Failure of Success Criterion 3.2.4 due to using two different labels for the same function on different Web pages within a set of Web pages
3.2.5 Understandable > Predictable > Change On Request
What? Give users full control of changes of context. Aims to eliminate potential confusion that may be caused by unexpected changes of context such as automatic launching of new windows, automatic submission of forms after selecting an item from a list.
How? Request to update button, redirect on servers side, use instant client side redirect, open new windows on user request, onchange event that does not change context. Content that initiates changes of context automatically only when user preferences allow can conform to this Success Criterion.
3.2.5 Understandable > Predictable > Change On Request
Failures
Failures-
New window launches upon input of text
automatic content change that cannot be disabled
context changes when focus removed from form element
windows open that were not requested by user
new window opens on page load
a meta redirect on a time limit
uses meta refresh to reload the page
