Navigable

2.4 Navigable

2.4 Navigable

Provide means to help users navigate, find content, and determine where they are.

Bypass Blocks

(A)

2.4.1 Bypassing blocks

2.4.1 Bypass blocks

A mechanism is available to bypass blocks of content that are repeated on multiple web pages.

9.2.4.1 Areas can be skipped

Relevance and applicability

This guideline is relevant when implementing accessibility for your portal.

General implementation

Intrexx fulfils this guideline through its accessible layout.

Navigation elements, search and page content are marked with landmarks and can be skipped by the portal user.

More information

Identify Purpose: Clarify the purpose of icons, (control) elements and sections of a page

Page Titled

(A)

2.4.2 Add a title to the page

2.4.2 Page Titled

Web pages have titles that describe topic or purpose.

9.2.4.2 Meaningful document titles

Relevance and applicability

This guideline is relevant when implementing accessibility for your portal.

General implementation

The implementation of this guideline is primarily an editorial task for the application developer.

When creating pages, make sure to assign speaking, meaningful titles.

Detailed implementation

Focus Order

(A)

2.4.3 Focus sequence

2.4.3 Focus Order

If a web page can be navigated sequentially and the order of navigation affects meaning or usability, focusable components receive focus in an order that maintains meaning and usability.

9.2.4.3 Conclusive sequence for keyboard operation

Relevance and applicability

This guideline is relevant when implementing accessibility for your portal.

General implementation

The implementation of this guideline is primarily an editorial task for the application developer.

The tab order follows the page structure (DOM). It can also be set up manually.

More information

Keyboard

Link purpose (in context)

(A)

2.4.4 Link purpose (in context)

2.4.4 Link Purpose (In Context)

The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.

9.2.4.4 Meaningful link texts

Relevance and applicability

This guideline is relevant when implementing accessibility for your portal.

General implementation

The implementation of this guideline is primarily an editorial task for the application developer.

Multiple Ways

(AA)

2.4.5 Different methods

2.4.5 Multiple Ways

More than one way is available to find a web page within a set of web pages, unless the web page is the result or a step within a process.

9.2.4.5 Alternative access routes

Relevance and applicability

This guideline is relevant when implementing accessibility for your portal.

General implementation

Portal and application pages are accessible via the portal menu and the sitemap.

As an application developer, you can configure even more access paths. You can use the additional control "Breadcrumb trail" in the "Design" module for this purpose.

More information

Additional controls

Headings and Labels

(AA)

2.4.6 Headings and labels

2.4.6 Headings and Labels

Headings and labels describe a topic or purpose.

9.2.4.6 Meaningful headings and labels

Relevance and applicability

This guideline is relevant when implementing accessibility for your portal.

General implementation

The implementation of this guideline is primarily an editorial task for the application developer.

Focus Visible

(AA)

2.4.7 Focus visible

2.4.7 Focus Visible

Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.

9.2.4.7 Current position of the focus clearly

Relevance and applicability

This guideline is relevant when implementing accessibility for your portal.

General implementation

Intrexx fulfils this guideline through its accessible layout.

Location

(AAA)

2.4.8 Position

2.4.8 Location

Information about the user's location within a set of web pages is available.

Relevance and applicability

This guideline is relevant when implementing accessibility for your portal.

General implementation

Portal and application pages are accessible via the portal menu and the sitemap.

As an application developer, you can configure even more access paths. You can use the additional control "Breadcrumb trail" in the "Design" module for this purpose.

More information

Additional controls

Link Purpose (Link Only)

(AAA)

2.4.9 Link purpose (pure link)

2.4.9 Link Purpose (Link Only)

A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general.

Description

This success criterion is related to the success criterion Link purpose (in context).

Relevance and applicability

This guideline is relevant when implementing accessibility for your portal.

General implementation

The implementation of this guideline is primarily an editorial task for the application developer.

Section Headings

(AAA)

2.4.10 Section headings

2.4.10 Section Headings

Section headings are used to organize the content.

Relevance and applicability

This guideline is relevant when implementing accessibility for your portal.

General implementation

The implementation of this guideline is primarily an editorial task for the application developer.

As an application developer, you can use any HTML structural elements in a Static Text field (for example).

As a portal user, for example, you can use the "Content Editor" element to create section headings.

More information

Content Editor / Content View