Keyboard Accessible

2.1 Accessible via keypad

2.1 Keyboard Accessible

Make all functionality available from a keyboard.

Keyboard

(A)

2.1.1 Keyboard

2.1.1 Keyboard

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.

9.2.1.1 Usable without mouse

Relevance and applicability

This guideline is relevant when implementing accessibility for your portal. It is one of the best practicesHow to make your pages accessible - Best practices).

General implementation

Central points of this guideline are fulfilled through the use of the barrier-free layout of Intrexx. This includes navigation in the portal menu, for example. Keyboard operation is not possible for certain elements so we recommend they are not used for accessible pages. You can find an overview of these elements in the section Overview of Intrexx application elements

Detailed implementation

A suitable tab sequence is important for operation via the keyboard. This should result in a coherent arrangement of elements on a page (DOM order). You can override the DOM order manually via the tab index if required.

Define tab order

You can specify the tab order with the tab index, i.e. the order in which users move from one input element to the next on a page using the TAB key.

Step-by-step guide

  1. Select the page you want to use to set the tab index.

  2. Right click on it.

  3. Select the "Set tab index..." entry in the context menu from.

    The "Set tab index..." dialog box is displayed.

  4. Move the elements for which you want to set the tab index from the "Elements without tab index" area to the "Elements with tab index" area.

  5. Sort the elements in the "Elements with tab index" area.

  6. Click on "OK".

Set focus – Input fields and buttons

Via the main menu "Edit" / Set focus or via the context menu, input fields and buttons with the type "Button" or "Text" can be given the focus when the page is loaded. One or more elements of the page can be set with "Set focus". When the page is loaded, the focus is set to the first visible element.

Set focus – Pages

In the page properties, you can specify that the page does not set a focus. If "Set focus" is not set for any element on a page, the first focusable element on the page is automatically determined and the focus is set there. The following exceptions apply:

  • The focus is not set on fields in free-form tables

  • The focus is not set within portlets

  • On pages with a tab index, the focus is set on the element with tab index 1

Focus

You should not set focus for pages that open in the main window. This means you should activate the "Do not set focus" checkbox.

For pages that open as a tooltip (popup dialog), you should set a focus. This means that you should not activate the "Do not set focus" checkbox. Please note that you should generally - if possible - avoid using tooltips.

No Keyboard Trap

(A)

2.1.2 No Keyboard Trap

2.1.2 No keyboard trap

If keyboard focus can be moved to a component of the page through a keyboard interface, then focus can be moved away from that component using only the keyboard interface; if this requires using more than arrow or tab keys modified by non-auxiliary keys (such as Shift, Control, or Command) or other common exit methods, then the user is informed of the method for moving focus.

9.2.1.2 No keyboard trap

Relevance and applicability

This guideline is relevant when implementing accessibility for your portal. It is one of the best practicesHow to make your pages accessible - Best practices).

General implementation

There are no keyboard traps in Intrexx.

Keyboard (no exception)

(AAA)

2.1.3 Keyboard (no exception)

2.1.2 No Keyboard Trap

All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.

Description

This success criterion is a more stringent version of the Keyboard success criterion (see above). The aim is to ensure that all content can be operated using the keyboard.

Central points of this guideline are fulfilled through the use of the barrier-free layout of Intrexx. This includes navigation in the portal menu, for example. Keyboard operation is not possible for certain elements so we recommend they are not used for accessible pages. You can find an overview of these elements in the section Overview of Intrexx application elements

Character Key Shortcuts

(A)

2.1.4 Character key commands

2.1.4 Character Key Shortcuts

If a keyboard shortcut in the content is only implemented with letters (both upper and lower case), punctuation marks, numbers or symbols, then at least one of the following conditions is met:

Can be switched off A mechanism is available to switch off the command;

Reassignable A mechanism is available to reassign the keyboard shortcut so that it contains one or more non-printable keys (e.g. Ctrl, Alt);

Only active with focus The keyboard shortcut for a component of the user interface is only active if this component has the focus.

9.2.1.4 Keyboard shortcuts can be switched off or customized

Relevance and applicability

This guideline is relevant when implementing accessibility for your portal.

General implementation

There are no keyboard shortcuts for portal and application pages by default.