Page 90 - GIGW2

CH 07 Development

7.4.2 Documents

a. Government websites shall have a lot of information in the form of documents
such as Acts, Rules, Schemes, Gazettes, Forms, Circulars and Notifications.
Accessibility and usability of these documents by all citizens is as important as
that of the entire website. Departments MUST either use HTML format or
any other format that makes the document accessible. In case documents are
published in a format other than HTML format, departments MUST provide
a link to the website from where the document reader can be downloaded free
of cost.
b. When the document has been provided in a format other than HTML,
websites should include a text description of the document, including the
title, file type, file size, and effective date. This will ensure that visitors have a
reasonable understanding of what to expect when they view the document.

c. When the document has been provided in a format other than HTML,
websites should include a text description of the document, including the
title, file type, file size, and effective date. This will ensure that visitors have a
reasonable understanding of what to expect when they view the document.
The document should be properly tagged and should not contain scanned
images of text (Ref. 6.6.1).This will ensure that the document is accessible to
screen reader users (refer guidelines website web.guidelines.gov.in for details).
7.5 R

Ready Reference for Developers

a. It MUST be ensured that in content implemented using markup languages,
elements have complete start and end tags, elements are nested according
to their specifications, elements do not contain duplicate attributes, and
IDs , if any, are unique, except where the specifications allow these features.
This helps to ensure that user agents, including assistive technologies, can
accurately interpret and parse content. If the content cannot be parsed, then
different user agents may present it differently. Some user agents use “repair
techniques” to render poorly coded content. Since repair techniques vary
among user agents, authors cannot assume that content will be rendered
correctly by specialized user agents. (Ref. WCAG 4.1.1)

b. Labels or instructions MUST be provided when content requires user
input (for example in forms). Text instructions that describe the input
must be provided at the beginning of a form or set of fields. Elements
associated with input must be labeled to ensure that information about
the input field is spoken by screen readers when the field receives focus.

76