Predictable

3.2 Predictable

3.2 Predictable

Make sure that websites look and function in a predictable way.

In Focus

(A)

3.2.1 When Focused

3.2.1 On Focus

If any component of the user interface receives focus, this does not trigger a context change.

9.3.2.1 No Unexpected Context Changes When Focus Shifts

Description

An element that can trigger an event when it receives focus must not alter the context. Examples of changing the context when gaining focus include:

  • Forms are submitted automatically when a component receives focus;

  • A new one is started when a component receives focus;

  • The focus shifts to another element when that element receives the focus;

Relevance and Applicability

This guideline is relevant when implementing accessibility for your portal.

General Implementation

Intrexx does not trigger any unexpected context changes. As an application developer, it is your responsibility to avoid implementing any unexpected context changes.

When entering

(A)

3.2.2 When entering

3.2.2 On Input

Changing the settings of any user interface component does not automatically change the context, unless the user was informed of this behavior before using the component.

9.3.2.2 No Unexpected Context Changes During Input

Relevance and Applicability

This guideline is relevant when implementing accessibility for your portal.

General Implementation

Intrexx does not trigger any unexpected context changes when data is entered.

Using filters may result in updates. This is the case, for example, when filtering tables. However, this is an expected change.

As an application developer, make sure that changes occur below the respective input element.

As an application developer, it is your responsibility to avoid implementing any unexpected context changes.

Consistent Navigation

(AA)

3.2.3 Consistent Navigation

3.2.3 Consistent Navigation

Navigation mechanisms that are repeated on multiple web pages within a set of web pages appear in the same relative order each time they are repeated, unless a change is initiated by the user.

9.3.2.3 Consistent Navigation

Relevance and Applicability

This guideline is relevant when implementing accessibility for your portal.

General Implementation

Portals created with Intrexx automatically feature consistent navigation.

Notwithstanding the above, the view may appear before the login dialog or authentication on the portal.

Consistent Detection

(AA)

3.2.4 Consistent Detection

3.2.4 Consistent Identification

Elements with the same functionality within a set of web pages are consistently recognized.

9.3.2.4 Consistent Naming

Relevance and Applicability

This guideline is relevant when implementing accessibility for your portal.

General Implementation

Implementing this guideline is primarily an editorial task for the application developer.

Changes upon request

(AAA)

3.2.5 Changes Upon Request

3.2.5 Change on Request

Changes to the context are triggered only by user request, or there is a mechanism to disable such changes.

Description

In some cases, it may be helpful to ensure that context changes occur only when the user actively triggers them and, if necessary, is notified of the context change beforehand.

People who are blind or visually impaired have difficulty determining when the visual context has changed, such as when a new dialog box appears. In this case, a warning before the context changes can minimize confusion if the user notices that the Back button no longer behaves as expected.

Relevance and Applicability

This guideline is relevant when implementing accessibility for your portal.

General Implementation

As an application developer, it is your responsibility to indicate a change in context when necessary.