Application Procedures
Make it easier for users to access features using input methods other than the keyboard.
Pointing Gestures
(A)
All features that use multi-touch or path-based gestures for operation can be operated with a single pointer without using a path-based gesture, unless a multi-touch or path-based gesture is essential.
9.2.5.1 Alternatives for Complex Pointer Gestures
Relevance and Applicability
This success criterion is not relevant in the context of Intrexx.
Intrexx does not use or require any complex pointer gestures.
Pointer Removal
(A)
For a feature that can be operated using a single pointer, at least one of the following conditions is met:
No down event. The pointer's down event is not used to execute any part of the function;
Cancel or Undo The function completes with the Up event, and there is a mechanism to cancel the function before it completes or to undo it after it has completed;
Up Event Reversal (Up Reversal) The Up Event reverses any result of the preceding Down Event;
Essential: It is essential to complete the function when the down event occurs.
9.2.5.2 Pointer gesture inputs can be canceled or revoked
Relevance and Applicability
This success criterion is not relevant in the context of Intrexx.
Intrexx does not use or require pointers.
If you, as an application developer, implement such an element or feature, you must ensure that it is implemented correctly.
Label in the name
(A)
For user interface components with labels that contain text or images of text, the name consists of the text that is visually displayed.
9.2.5.3 Visible Label as Part of the Accessible Name
Description
Visible labels for control elements should also appear in the control element's name, which can be determined programmatically. This applies, for example, to links, text field labels, buttons, and checkboxes.
Relevance and Applicability
This success criterion is not relevant in the context of Intrexx.
General Implementation
In Intrexx, you can mark up elements with ARIA roles and attributes. This allows you to make labels accessible to screen readers, for example.
More Information
Assign ARIA roles and attributes
Motion-Activated
(A)
Features that can be activated by the movement of devices or users can also be activated through elements of the user interface, and the response to movement can be disabled to prevent accidental activation. The following exceptions apply:
Supported Interface: This gesture is used to operate functions via an accessibility interface;
Indispensable: Movement is indispensable for function, and without it, the activity would be rendered invalid.
9.2.5.4 Alternatives for Promoting Physical Activity
Relevance and Applicability
This success criterion is not relevant in the context of Intrexx.
This feature is not supported in Intrexx
Target value
(AAA)
The target size for pointer input is at least 44 by 44 CSS pixels. The following exceptions apply:
Equivalent: The target is accessible 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 within a sentence or block of text;
Control by the user agent: The size of the target is determined by the user agent and is not modified by the author;
Essential: A specific representation of the goal is essential for conveying the information.
Description
This success criterion is intended to ensure that the areas of elements are large enough so that users can easily select or interact with them, even if the user is using a small touchscreen device, has limited dexterity, or has difficulty interacting with small areas for other reasons. For example, mice and similar pointing devices can be difficult for these users to operate, and an element with a larger surface area would help them select the target.
Relevance and Applicability
General Implementation
If you, as an application developer, implement such an element or feature, you must ensure that it is implemented correctly.
Input mechanisms available simultaneously
(AAA)
2.5.6 Simultaneously Available Input Mechanisms
2.5.6 Concurrent Input Mechanisms
Web content shall not restrict the use of the input methods available on a platform, unless such restriction is indispensable or necessary to ensure the security of the content or to accommodate user preferences.
Description
This success criterion ensures that people can use and switch between different input methods when interacting with portal content. One example of this is the ability to switch between using an application with the mouse and using it with the keyboard.
Relevance and Applicability
General Implementation
The Intrexx portal and application pages can be navigated using either the mouse or the keyboard.