Make sure Web pages appear and operate in predictable ways.
On Focus
(A)
When any user interface component receives focus, it does not initiate a change of context.
9.3.2.1 No unexpected context change on focus
Description
An element that can initiate an event when it receives focus must not change the context. Examples of changing context when a component receives focus include, but are not limited to:
-
Forms submitted automatically when a component receives focus;
-
New windows launched when a component receives focus;
-
Focus is changed to another component when that component receives focus;
Relevance and applicability
General implementation
Intrexx does not initiate any unexpected change of context. It is your responsibility as a Web author not to implement unexpected changes of context.
On Input
(A)
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.
9.3.2.2 No unexpected context change on input
Relevance and applicability
General implementation
Intrexx does not initiate an unexpected change of context on input.
Updates may occur when using filters. This is the case, for example, when filtering tables. However, this is an expected change.
As a Web author, make sure that changes take place below the input element.
It is your responsibility as a Web author not to implement unexpected context changes.
Consistent Navigation
(AA)
Navigation mechanisms that are repeated on multiple web pages within a set of web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user.
Relevance and applicability
General implementation
Portals created with Intrexx automatically have consistent navigation.
Apart from that, it can be viewed before the login dialog or authentication to the portal.
Consistent Identification
(AA)
3.2.4 Consistent Identification
3.2.4 Consistent Identification
Components that have the same functionality within a set of web pages are identified consistently.
9.3.2.4 Consistent designation
Relevance and applicability
General implementation
Change on Request
(AAA)
Changes of context are initiated only by user request or a mechanism is available to turn off such changes.
Description
It can be helpful if any context changes take place only if initiated by the user, and also if the user is notified of the context change in advance.
Individuals who are blind or have low vision may have difficulty knowing when a visual context change has occurred, such as a new window popping up. In this case, warning users of context changes in advance minimizes confusion when the user discovers that the back button no longer behaves as expected.
Relevance and applicability
General implementation
It is your responsibility as a Web author to highlight any changes in context.
Email us