Page 91 - GIGW2

Guidelines

for Indian Government Apps & Websites

(Ref. WCAG 3.3.2)

c. In situations where web functions are time-dependent, (for example, filling out
online form) it will be difficult for people with disabilities such as blindness,
low vision, dexterity impairments, and cognitive limitations to perform the
required functions before a time limit occurs. This may render the service
inaccessible to them. It must therefore be ensured that such users are given
adequate time to interact with Web content whenever possible. For each time
limit that is set by the content, the user MUST be allowed to turn off the time
limit, adjust the default setting before encountering it or is warned before
time expires and given option to extend the time limit with a simple action
(for example, “press the spacebar”). (Ref. WCAG 2.2.1)

Activities that essentially require a time limit (for example an online auction)
or the time limit is too long (say 20 hours) are exceptions.

d. Many users including the visually challenged cannot perceive shape, size or
use information about location or orientation. For such users the content that
relies on knowledge of the shape or position of objects becomes inaccessible
(for example, “round button” or “button to the right”). Hence It MUST be
ensured that instructions provided for understanding and operating content
do not rely solely on sensory characteristics of components such as shape,
size, visual location, orientation, or sound. Additional information needs to
be provided to clarify anything that is dependent on this kind of information.
(Ref. WCAG 1.3.3)
e. If an input error is automatically detected, the error MUST be described to
the user in text. The error message should be as specific as possible. This will
ensure that users are aware that an error has occurred and can determine what
is wrong. Describing the error in text in addition to highlighting the errors
will help screen reader users, who cannot distinguish colour and users with
cognitive disorders who have difficulty in perceiving the meaning of other
visual cues. (Ref. WCAG 3.3.1)

f. All functionality of the content MUST be operable through a keyboard
interface without requiring specific timings for individual keystrokes, except
where input depends on the path of the user’s movement (for example,
drawing freehand curves or using handwriting to write). (Ref. WCAG 2.1.1)

g. Whenever a web page is rendered using plug-ins or embedded applications, it
is possible that functionality of the Web page restricts the keyboard focus to
a subsection of the content, unless the user knows how to leave that state and
“untrap” the focus. This situation may affect navigation for people who rely on
a keyboard or keyboard interface to use the Web, including visually challenged

©2017,NIC 77