Page 121 - GIGW2

Guidelines

for Indian Government Apps & Websites

It sometimes takes many attempts to find out the new elements and if such
interactions are time sensitive, a timeout could occur and the user would have
to start all over again. Even without timeouts, new users could find it difficult to
manage such interactions thus impacting the user experience. Therefore focus
MUST be brought to the active UI control.

11.4.10 Custom actions for context specific UI
When a UI control has context specific menu items, users MUST be
informed that such a menu is present and must be able to activate those
menu items. A Custom Action is an effective technique to support such an
interaction. Both Android and iOS provide Custom Actions that are available
to assistive technology users. When an element with a custom action is focused,
assistive technology lets the user know that such actions are available and then
users can use well known gestures to perform those actions. Alternatively, use
the accessibility API to report to the user what new UI elements are available
and where such elements are present on the screen. This way users can locate
those elements. This technique should only be used if Custom Actions are not
available.
11.4.11 Logical and meaningful sequence

Screen reader mobile users rely on gestures to navigate and interact with the
content and the UI controls. Content when navigated using the screen reader
gestures, MUST form a meaningful sequence. The controls on the mobile
screens and the interaction produced need to be logical.

11.4.12 Screen orientation
Assistive technology users could lock screen orientation to avoid interference
with their interaction with the device. Hence the following should be followed
while handling screen orientation:
a. If the user has turned on “Locked Orientation” option for iOS or disabled
the Auto-rotate screen option for Android, then the app should not try
to change the screen orientation.
b. If Screen orientation change is not disabled then it should be ensured
that the screen orientation change is not disruptive and the focus does
not move from the focused screen element.
c. Screen orientation change should be reported using accessibility API.

d. Report Screen orientation at the start if it is different from the default
setting when screen orientation change is disabled. Otherwise,
the change should be reported every time the orientation changes.

©2017,NIC 107