Accessibility View Settings in the Web Profile

An Accessibility View is a customized version of a publication designed to be optimized for users who rely on screen readers. The purpose of an Accessibility View is to improve the user experience for people with, for example, visual impairments.

Accessibility Views are part of the effort to comply with WCAG (Web Content Accessibility Guidelines), a set of guidelines aimed at making the web more accessible to all users.

In the Web Profile, you can create your own Accessibility View.

Here, you can select which information about objects and models should be displayed in a table. This optimizes the information that is most important to the user while ensuring compatibility with screen readers. As a result, users can access information in a more tailored and accessible way.

Configuring an Accessibility View

Step 1 – Enable the Accessibility View

Open the Web Profile and click Edit in the upper-right corner above the search field.

Step 2 – Configuration

The Title field allows you to change the name of the view.

Each model type has its own settings that determine which information is read by the screen reader. Configure each model type that should be supported by the Accessibility View.

Once a model type has been selected, choose the objects that should be read aloud. By default, all objects are selected. For process models, we recommend including activities and processes.

The section following the object selection contains the settings for what should be read aloud for both the model and its objects. These settings work similarly to publishing and report profiles, where relationships, descriptions, and fields can be added.

When relationships are included, the screen reader will also read any related objects connected to, for example, the activity.

Clarification: You do not need to add roles to the object list if the roles are already related to the objects. They will be read aloud together with the activity and its relationships.

Even if document links are included, the documents themselves will not be read aloud. However, users can still open the linked documents.

Lists and matrices are not supported in the Accessibility View.

Repeat these steps for each model type and save your changes.

Step 3 – Publish

Publish the material as usual.

A new button, displayed as a table icon, will now be available below the search field in both the Web Profile and the published material. Accessibility Mode can be activated either by clicking this button or by using the keyboard shortcut Alt + A.