Input modalities

2.5 Input Modalities

2.5 Input Modalities

Make it easier for users to operate functionality through various inputs beyond keyboard.

Pointer Gestures

(A)

2.5.1 Pointer Gestures

2.5.1 Pointer Gestures

All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential.

9.2.5.1 Alternatives to complex pointer gestures

Relevance and applicability

This success criterion is not relevant to Intrexx.

In Intrexx, no complex pointer gestures are used or required.

Pointer Cancellation

(A)

2.5.2 Pointer Cancellation

2.5.2 Pointer Cancellation

For functionality that can be operated using a single pointer, at least one of the following is true:

No Down-Event The down-event of the pointer is not used to execute any part of the function;

Cancel or Undo Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;

Up Reversal The up-event reverses any outcome of the preceding down-event;

Essential Completing the function on the down-event is essential.

9.2.5.2 Pointer gesture inputs can be canceled or revoked

Relevance and applicability

This success criterion is not relevant to Intrexx.

No pointers are used or required in Intrexx.

If as an application developer, you implement such elements or features, you have to ensure they are implemented correctly.

Label in name

(A)

2.5.3 Label in name

2.5.3 Label in name

For user interface components with labels that include text or images of text, the name contains the text that is presented visually.

9.2.5.3 Visible labeling part of the accessible name

Description

Visible labels of control elements should also appear in the programmatically determinable name of the control element. For example, this is true for links, text field labels, buttons or checkboxes.

Relevance and applicability

This success criterion is not relevant to Intrexx.

General implementation

In Intrexx, you have the option of labeling elements with ARIA roles and attributes. By using roles and attributes, you can make captions accessible to screen readers, for example.

More information

Assign ARIA roles and attributes

Motion Actuation

(A)

2.5.4 Motion Actuation

2.5.4 Motion Actuation

Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation. The following exceptions apply:

Supported Interface The motion is used to operate functionality through an accessibility supported interface;

Essential The motion is essential for the function and doing so would invalidate the activity.

9.2.5.4 Alternatives to motion activation

Relevance and applicability

This success criterion is not relevant to Intrexx.

This functionality is not supported in Intrexx

Target Size

(AAA)

2.5.5 Target Size

2.5.5 Target Size

The size of the target for pointer inputs is at least 44 by 44 CSS pixels. The following exceptions apply:

Equivalent The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels;

Inline The target is in a sentence or block of text;

User Agent Control The size of the target is determined by the user agent and is not modified by the author;

Essential A specific representation of the target is essential to the information being conveyed.

Description

The intent of this success criterion is to ensure that the areas of elements are large enough for users to easily navigate or operate, even if the user is using a small touch screen device, has limited dexterity, or has difficulty operating small surface areas for other reasons. For example, mice and similar pointing devices can be hard to use for these users, and an element with a larger surface area would help activate the target.

Relevance and applicability

This guideline is relevant when making your portal accessible.

General implementation

If as an application developer, you implement such elements or features, you have to ensure they are implemented correctly.

Concurrent Input Mechanisms

(AAA)

2.5.6 Concurrent Input Mechanisms

2.5.6 Concurrent Input Mechanisms

Web content does not restrict use of input modalities available on a platform except where the restriction is essential, required to ensure the security of the Content, or required to respect user settings.

Description

This success criterion is about people being able to use and switch between different input methods when interacting with portal content. An example of this is the ability to switch between operating an application with the mouse and with the keyboard.

Relevance and applicability

This guideline is relevant when making your portal accessible.

General implementation

The Intrexx portal and application pages can be operated with both the mouse and the keyboard.