Keyboard Accessible

2.1 Keyboard Accessible

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 making your portal accessible. It is one of the best practices How to make your pages accessible - Best practices).

General implementation

The main aspects of this guideline are satisfied through the use of the accessible Intrexx layout. 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. An overview of these elements can be found in the section Overview of Intrexx application elements.

Detailed implementation

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

Set tab index

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..." item in the context menu.

    The "Set Tab Index..." dialog box is displayed.

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

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

  6. Click on "OK".

Set focus – Input fields and buttons

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

Set focus – Pages

You can define that a page should not set a focus in the Page properties. If "Set focus" has not been defined for any elements on a page, the initially focused element on the page is determined automatically. The following exceptions apply:

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 you should not activate the "Do not set focus" checkbox. Note that you should generally refrain from using tooltips if possible.

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 using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.

9.2.1.2 No keyboard trap

Relevance and applicability

This guideline is relevant when making your portal accessible. It is one of the best practices How 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 intent is that all content can be operated through a keyboard.

The main aspects of this guideline are satisfied through the use of the accessible Intrexx layout. 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. An overview of these elements can be found in the section Overview of Intrexx application elements.

Character Key Shortcuts

(A)

2.1.4 Character Key Shortcuts

2.1.4 Character Key Shortcuts

If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:

Turn off A mechanism is available to turn the shortcut off;

Remap A mechanism is available to remap the shortcut to include one or more non-printable keyboard keys (e.g. Ctrl, Alt);

Active only on focus The keyboard shortcut for a user interface component is only active when that component has focus.

9.2.1.4 Keyboard shortcuts can be disabled or adapted

Relevance and applicability

This guideline is relevant when making your portal accessible.

General implementation

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