Accessible via the keyboard

2.1 Accessible via the keyboard

2.1 Keyboard Accessibility

Make sure that all features are accessible via the keyboard.

Keyboard

(A)

2.1.1 Keyboard

2.1.1 Keyboard

All features of the content can be controlled via a keyboard interface without requiring a specific timing for individual keystrokes, unless the underlying function requires inputs that depend on the user's movement path and not just on the endpoints.

9.2.1.1 Can be used without a mouse

Relevance and Applicability

This guideline is relevant when implementing accessibility for your portal. It is considered one of the best practices (How to Make Your Web Pages Accessible - Best Practices).

General Implementation

The key requirements of this guideline are met through the use of Intrexx's accessible 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. You can find an overview of these elements in Overview of Intrexx Application Elements section " "

Implementation in Detail

A proper tab order is important for keyboard navigation. This should result from a logical arrangement of the elements on a page (DOM order). If necessary, you can manually override the DOM order using the tabindex attribute.

Set the 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

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

  2. Right click on it.

  3. From the context menu, select "Set Tab Index..." from.

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

  4. Move the elements for which you want to set the tabindex from the "Elements without tabindex" section to the "Elements with tabindex" section.

  5. Sort the elements in the "Elements with Tabindex" section.

  6. Click "OK."

Setting Focus - Input Fields and Buttons

You can set the focus on input fields and buttons of the "Button" or "Text" type when the page loads either via the "Edit" option in the main menu or via the context menu. You can use the "Set Focus" option to select one or more elements on the page. After loading, the first visible element will then receive focus.

Set Focus - Pages

In the page properties, you can specify that the page should not receive focus. If "Set Focus" is not set for any element on a page, the first focusable element on the page is automatically determined, and focus is set there. However, there are the following exceptions:

Focus

You should not set focus for pages that open in the main window. In other words, you should select the "Do not set focus" checkbox.

For pages that open as a tooltip (popup dialog), you should set a focus. In other words, you should not check the "Do not set focus" checkbox. Please note that, in general, you should avoid using tooltips whenever possible.

No Keyboard Trap

(A)

2.1.2 No Keyboard Trap

2.1.2 No Keyboard Trap

If the keyboard focus can be moved to a page element via a keyboard interface, then the focus can be moved away from that element using only the keyboard interface; if this requires the use of arrow or Tab keys that are not modified by modifier keys (such as Shift, Ctrl, or Command) or other standard exit methods, the user is informed of the method for moving the focus.

9.2.1.2 No Keyboard Trap

Relevance and Applicability

This guideline is relevant when implementing accessibility for your portal. It is considered one of the best practices (How to Make Your Web Pages Accessible - Best Practices).

General Implementation

There are no keyboard traps in Intrexx.

Keyboard (no exception)

(AAA)

2.1.3 Keyboard (no exceptions)

2.1.2 No Keyboard Trap

All features of the content can be controlled via a keyboard interface without requiring a specific timing for individual keystrokes.

Description

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

The key requirements of this guideline are met through the use of Intrexx's accessible 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. You can find an overview of these elements in Overview of Intrexx Application Elements section " "

Character Key Commands

(A)

2.1.4 Character Key Commands

2.1.4 Character Key Shortcuts

If a keyboard shortcut in the content consists only of letters (both uppercase and lowercase), punctuation marks, numbers, or symbols, then at least one of the following conditions is met:

Can be disabled A mechanism is available to disable the command;

Can be remapped: A mechanism is available to remap the keyboard shortcut so that it includes one or more non-printable keys (e.g., Ctrl, Alt);

Active Only When in Focus: The keyboard shortcut for a user interface element is active only when that element has focus.

9.2.1.4 Keyboard shortcuts can be disabled or customized

Relevance and Applicability

This guideline is relevant when implementing accessibility for your portal.

General Implementation

By default, there are no keyboard shortcuts for portal and application pages.