Show TOC

Screen Reader SupportLocate this document in the navigation structure

SAPUI5 application developers need to be aware of how the screen reader reads out the contents of the UI. Labels, headings and descriptions help you describe the contents and visual elements of an application.

General Recommendations
Table 1: Screen Reader Support - General Rules and Guidelines

Rules and Guidelines


Generate valid HTML

The screen reader software gets the information about the page directly from the DOM. Therefore, if the DOM is invalid, the information presented to the user might be invalid as well. Ideally, if the DOM is correct, the screen reader software will interpret it correctly. When you need to create new controls or change the HTML structure of existing ones for some reason, you have to check the validity of the resulting HTML.

Use titles for complex components

Complex controls like pages, panels and tables need a title to summarize the contents they hold. If you use the standalone Title control, make sure that it is associated with the element that needs the title.

   <Title id="rbGroupTitle" text="Select an option" textAlign="Center"/>

   <RadioButtonGroup columns="2" selectedIndex="2" ariaLabelledBy="rbGroupTitle">
         <RadioButton id="RB2-1" text="Option 1"/>
         <RadioButton id="RB2-2" text="Option 2" editable="false"/>
         <RadioButton id="RB2-3" text="Option 3"/>


Use labels

Make sure that all edit boxes, search fields and column headers have labels. If not, use the Label control and add one. Labels have to be connected to each control, for example by using one of the following:
  • labelFor=”…”

  • aria-label=”…”

  • aria-labelledby=”…”

  • placeholder=”…”

  • title=”…”

Titles in headings

For headings (table toolbar, page header, form toolbar, panel toolbar) the text should be in a sap.m.Title control (make sure that it is associated with the element that needs the title and, if not, add the reference using aria-labelledby).
   <Panel expandable="true">
         <Toolbar height="3rem">
            <Title text="Header"/>

            <Button icon="sap-icon://settings"/>
            <Button icon="sap-icon://drop-down-list"/>
         <Text text="Lorem ipsum"/>

Labels and descriptions for input controls

When using the Input control, always provide a label (make sure it is connected with the input). You can also use the description property to add additional information. For the input, the description is usually used for showing the unit of measurement (for example. "EUR").

         <Label text="Product price" labelFor="productPriceInput"/>
            description="EUR / 5 pieces"
            fieldWidth="60px" />


Empty labels in drop-down lists

In some cases, you may need to provide an empty option in a drop-down field such as Select. This way you want to indicate that none of the items in the drop-down is applicable, or offer the empty option as a way to clear the selection. In this case, you should properly label the empty option with (None) and not leave it blank.

The labelling on the empty option will be read by the screen reader and the end-user will be correctly informed about the semantics of the empty option.


The empty label (None) should always be the first item in the drop-down.

Tips for Testing

Start a screen reader, start the application, walk through the application using the keyboard and listen. For example, you can also use Virtual Cursor mode or similar functions of your screen reader because some elements do not need to have the focus to be readable by screen readers.

  • Is everything that you need to use the application read correctly?

    • Each element’s role, name, state, label, tooltip, further information (attached errors, usage hints)?

    • Is this the case for interactive and semantic/non-semantic elements?

    • Actively check that all visible UI elements are read.

  • Is it read correctly?

    • No duplicates?

    • No strange pronunciation, like reading English with German words or vice versa?

    • No nonsense, wrong values, another element’s attributes?

  • Are screen updates like application messages, dialogs (popups) and similar dynamic content read correctly and at the right time?