Make it easier for users to operate functionality through various inputs beyond keyboard.
Pointer Gestures
(A)
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 for 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)
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 part of the function;
Cancel or undo The function is completed with the Up event and there is a mechanism for canceling the function before completion or undoing it after completion;
Undo on Up event (Up Reversal) The Up event undoes every result of the previous Down event;
Indispensable Completing the function at the down event is indispensable.
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 you implement such an element or feature as an application developer, you must ensure that it is implemented correctly.
Label in name
(A)
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)
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 movement is used to operate functions via an accessibility-supporting interface;
Indispensable The movement is indispensable for the function and would invalidate the activity.
9.2.5.4 Alternatives for movement activation
Relevance and applicability
This success criterion is not relevant to Intrexx.
This functionality is not supported in Intrexx
Target size
(AAA)
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 via an equivalent link or control on the same page that is at least 44 by 44 CSS pixels in size;
Inline The target is located in a sentence or text block;
Control by the user agent The size of the target is determined by the user agent and is not changed by the author;
Indispensable A specific presentation of the objective is indispensable for the information to be conveyed.
Description
This success criterion is intended to ensure that the surfaces of elements are large enough for users to be able to control or operate them easily, even if the user is using a small touchscreen device, has limited dexterity or has difficulty operating small surfaces 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
General implementation
If you implement such an element or feature as an application developer, you must ensure that it is implemented correctly.
Concurrent Input Mechanisms
(AAA)
2.5.6 Simultaneously available 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
General implementation
The Intrexx portal and application pages can be operated with both the mouse and the keyboard.
Send us an e-mail