Page 119 - GIGW2

Guidelines

for Indian Government Apps & Websites

such as Voice over or Talk Back. labels that are embedded into an image must be
avoided as they cannot be parsed by screen readers. Hence it MUST be ensured
that Proper labels have been provided for all UI elements.
Following key points should be considered while labeling UI elements:

a. A label must be precise and clear: Think about the purpose that the UI
element serves. For example, label “Add to favourites” for adding an item to
favourites. Action verbs that describe the purpose of the UI element must be
used in order to provide appropriate labels.

b. Timely Update:In case the functionality of the UI element changes, the label
must be updated as well. For example, “Play” button must change to “Pause”
and vice versa for media files. Updated labels make it easy for the users to
interact with the app.

c. Role and state information should not be provided as the as part of label:
This information is provided separately through Accessibility API (described
in Practice 3).For instance, “Play ”button to be labeled as “Play”, and not
“Play button” because the button’s role will be indicated through accessibility
API.

d. Label strings should be localised: This is required for users using the
applications in different languages.
11.4.3 Role information for UI elements

Every UI element can be identified visually with its look and feel. As users with
blindness cannot perceive visual information, the role for a UI element MUST
be available programmatically so that assistive technology can report this
either through speech or Braille. In order to do so, use platform specific roles or
traits for standard UI elements. For example, a button is announced as “Button”
along with the label for assistive technology users. In case of custom UI elements,
use platform accessibility API to report the role information.

11.4.4 Hints for active UI controls

A Hint is a brief, localized phrase that describes the results of an action on a
UI control. It is like a tool tip that lets the user find out how to interact with
the UI control. Hints are only required for UI controls that allow users some
interaction, and are not required for UI elements such as labels or plain text.
In case of custom UI controls, hints also report the screen reader gestures that
users could perform to interact with the control. The standard UI controls have
hints supplied by the APIs, but those hints might have to be changed depending
on the usage. It MUST be ensured that hints are provided for all active UI
control elements.

©2017,NIC 105