EXPERIMENT 1

Aim: Check and List down Government guidelines for creating a website.
Guidelines for Indian Government Websites (GIGW):
The National Informatics Centre (NIC) formulated the Guidelines for Indian Government
Websites (GIGW) in the year 2009. GIGW aims to ensure quality and accessibility of
government guidelines, by offering guidance on desirable practices covering the entire lifecycle
of websites, web portals and web applications, right from conceptualization and design to their
development, maintenance and management. The Department of Administrative Reforms and
Public Grievances made the same a part of the Central Secretariat Manual of Office Procedure.
Guidelines:
1. Quality: Guidelines and attributes:
1.1 Association to government is demonstrated by the use of emblem/logo in proper ratio and
color, prominently displayed on the homepage of the website or home screen of the app.
1.2 Ownership information is displayed on the homepage and on all important entry
pages/screens of the website/app and each subsequent page/screen is a standalone entity in
terms of ownership, navigation and context of content.
1.3 Source of all documents, not owned by the dept. that have been reproduced in part or full,
should be mentioned.
1.4 Due permissions have been obtained for publishing any content protected by copyright.
1.5 Homepage of the website should displays the last updated date.
1.6 Complete information including title, size, format and usage instructions is provided for all
downloadable material.
1.7 In respect of each circular, notification, document, form, scheme, service and recruitment
notice, the following should be clearly listed on the website/app: Complete title, Language (if
other than English), Purpose/procedure to apply (as applicable), Validity (if applicable)
1.8 All outdated Announcements, Tenders, Recruitment notices, News and Press Releases are
removed from the website/app and/or placed into the archives as per the archival policy.
1.9 All information about the government organization which is useful to users is present in the
‘About us’ section and a mechanism is in place to keep the information up to date.
1.10 Website should have a ‘Contact us’ page providing complete contact details of important
functionaries in the government organization and this should be linked from the homepage
and all relevant places on the website.
1.11 Feedback should be collected through online forms and a mechanism is in place to ensure
timely response to feedback/queries received through the website.
1.12 Website should provide a prominent link to the ‘National Portal’ from the homepage and
webpages belonging to the ‘National Portal’ load in the new browser window.
1.13 The website should be tested on multiple browsers. Hindi/Regional language fonts have
been tested on popular browsers for any inconsistency (loss of layout).
1.14 The website should have readily available Help section linked from all pages of the
website.

1
1.15 Website uses Cascading Style Sheets (CSS) to control layouts/styles and incorporates
responsive design features to ensure that the interface displays well on different screen sizes.
1.16 Website should be readable even when style sheets are switched off or not loaded.
1.17 Proper page title and language attribute along with metadata for page like keywords and
description are appropriately included.
1.18 Minimum content as prescribed in the guidelines is present on the homepage and all
subsequent pages/screens.
1.19 Data tables have been provided with necessary tags/markup.
1.20 Content of the web page prints correctly on an A4 size paper
1.21 Website is in the nic.in or gov.in domain. Educational Institutions and Research and
Academic Institutions, which are eligible for registration under ‘gov.in’ may use ‘edu.in’,
‘res.in’ or ‘ac.in’ domains.
1.22 API integration with key government platforms (India Portal, DigiLocker, Aadhaar,
Single-Sign-On, MyGov, Data Platform, MyScheme) and similar websites of the government
organization must be enabled for seamless exchange of Information and data.
The government organisation must ensure a consistent user experience and visual identities
across all its websites/apps.
1.23 Websites/apps must provide integration with popular social media.
1.24 The language is free from spelling and grammatical errors.

2. Accessibility: Guidelines and attributes

2.1 All non-text content that is presented to the user has a text alternative that serves the
equivalent purpose, except for the situations listed below:
a. Controls, Input: If non-text content is a control or accepts user input, then it has a name
that describes its purpose
b. Time-Based Media: If non-text content is time-based media, then text alternatives at
least provide descriptive identification of the non-text content
c. Test: If non-text content is a test or exercise that would be invalid if presented in text,
then text alternatives at least provide descriptive identification of the non-text content
d. Sensory: If non-text content is primarily intended to create a specific sensory experience,
then text alternatives at least provide descriptive identification of the non-text content
e. CAPTCHA: If the purpose of non-text content is to confirm that content is being
accessed by a person rather than a computer, then text alternatives that identify and
describe the purpose of the non-text content are provided and alternative forms of
CAPTCHA using output modes for different types of sensory perception are provided to
accommodate different disabilities
f. Decoration, Formatting, Invisible: If non-text content is pure decoration, is used only for
visual formatting, or is not presented to users, then it is implemented in a way that it can
be ignored by assistive technology.
2.2 For pre-recorded audio-only and pre-recorded video-only media, the following are true,
except when the audio or video is a media alternative for text and is clearly labelled as such:
a. Pre-recorded Audio-only: An alternative for time-based media is provided that presents
equivalent information for pre-recorded audio-only content

2
 b. Pre-recorded Video-only: Either an alternative for time-based media or an audio track is
provided that presents equivalent information for pre-recorded video-only content.
2.3 Captions are provided for all pre-recorded audio content in synchronized media, except
when the media is a media alternative for text and is clearly labelled as such.
2.4 An alternative for time-based media or audio description of the pre-recorded video content
is provided for synchronized media, except when the media is a media alternative for text and
is clearly labelled as such.
2.5 Captions are provided for all live audio content in synchronized media.
2.6 Audio description is provided for all pre-recorded video content in synchronized media.
2.7 Information, structure and relationships conveyed through presentation can be
programmatically determined or are available in text.
2.8 When the sequence in which content is presented affects its meaning, a correct reading
sequence can be programmatically determined.
2.9 Instructions provided for understanding and operating content do not rely solely on sensory
characteristics of components such as shape, color, size, visual location, orientation, or
sound.
2.10 Content does not restrict its view and operation to a single display orientation, such as
portrait or landscape, unless a specific display orientation is essential.
2.11 The purpose of each input field collecting information about the user can be
programmatically determined when the input field serves a purpose identified in the Input
Purposes for User Interface Components section; and The content is implemented using
technologies with support for identifying the expected meaning for form input data.
2.12 Color is not used as the only visual means of conveying information, indicating an action,
prompting a response, or distinguishing a visual element.
2.13 If any audio on a Web page plays automatically for more than 3 seconds, either a
mechanism is available to pause or stop the audio, or a mechanism is available to control
audio volume independently from the overall system volume level.
2.14 The visual presentation of text and images of text has a contrast ratio of at least 4.5:1,
except for the following:
a. Large Text: (18 pt. or 14 pt. bold) Large-scale text and images of large-scale text have
a contrast ratio of at least 3:1
b. Incidental: Text or images of text that are part of an inactive user interface component,
that are pure decoration, that are not visible to anyone, or that are part of a picture that
contains significant other visual content, have no contrast requirement
c. Logotypes: Text that is part of a logo or brand name has no contrast requirement.
2.15 Except for captions and images of text, text can be resized without assistive technology
up to 200 percent without loss of content or functionality.
2.16 If the technologies being used can achieve the visual presentation, text is used to convey
information rather than images of text except for the following:
a. Customizable: The image of text can be visually customized to the user’s requirements
b. Essential: A particular presentation of text is essential to the information being
conveyed
c. Use of images for representing text should be limited.

3
2.17 Content can be presented without loss of information or functionality and without
requiring scrolling in two dimensions for:
a. Vertical scrolling content at a width equivalent to 320 CSS pixels
b. Horizontal scrolling content at a height equivalent to 256 CSS pixels
c. Except for parts of the content which require a two-dimensional layout for usage or
meaning.
2.18 The visual presentation of the following has a contrast ratio of at least 3:1 against
adjacent color:
a. User Interface Components: Visual information required to identify user interface
components and states, except for inactive components or where the appearance of the
component is determined by the user agent and not modified by the author
b. Graphical Objects: Parts of graphics required to understand the content, except when a
particular presentation of graphics is essential to the information being conveyed.
2.19 In content implemented using markup languages that support the following text style
properties, no loss of content or functionality occurs by setting all of the following and by
changing no other style property:
a. Line height (line spacing) to at least 1.5 times the font size
b. Spacing following paragraphs to at least 2 times the font size
c. Letter spacing (tracking) to at least 0.12 times the font size
d. Word spacing to at least 0.16 times the font size
2.20 Where receiving and then removing pointer hover or keyboard focus triggers additional
content to become visible and then hidden, the following are true:
a. Dismissible: A mechanism is available to dismiss the additional content without
moving pointer hover or keyboard focus unless the additional content communicates an
input error or does not obscure or replace other content
b. Hover-able: If pointer hover can trigger the additional content, then the pointer can be
moved over the additional content without the additional content disappearing
c. Persistent: The additional content remains visible until the hover or focus trigger is
removed, the user dismisses it, or its information is no longer valid.
2.21 All functionality of the content is operable through a keyboard interface without requiring
specific timings for individual keystrokes, except where the underlying function requires
input that depends on the path of the user’s movement and not just the endpoints.
2.22 If keyboard focus can be moved to a component of the page using a keyboard interface,
then focus can be moved away from that component using only a keyboard interface and, if it
requires more than unmodified arrow or tab keys or other standard exit methods, the user is
advised of the method for moving focus away.
2.23 If a keyboard shortcut is implemented in content using only letter (including upper- and
lower-case letters), punctuation, number, or symbol characters, then at least one of the
following is true:
a. Turn off: A mechanism is available to turn the shortcut off
b. Remap: A mechanism is available to remap the shortcut to include one or more non-
printable keyboard keys

4
 c. Active only on focus: The keyboard shortcut for a user interface component is only
active when that component has focus.
2.24 For each time limit that is set by the content, at least one of the following is true:
a. Turn off: The user is allowed to turn off the time limit before encountering it; or
b. Adjust: The user is allowed to adjust the time limit before encountering it over a wide
range that is at least ten times the length of the default setting; or
c. Extend: The user is warned before time expires and given at least 20 seconds to extend
the time limit with a simple action (for example, “press the spacebar”) and the user is
allowed to extend the time limit at least ten times; or
d. Real-time Exception: The time limit is a required part of a real-time event (for
example, an auction) and no alternative to the time limit is possible; or
e. Essential Exception: The time limit is essential and extending it would invalidate the
activity; or
f. 20 Hour Exception: The time limit is longer than 20 hours.
2.25 For moving, blinking, scrolling, or auto-updating information, all of the following are
true: Moving, blinking, scrolling: For any moving, blinking or scrolling information that
starts automatically, lasts more than five seconds and is presented in parallel with other
content, there is a mechanism for the user to pause, stop, or hide it unless the movement,
blinking, or scrolling is part of an activity where it is essential and For any auto-updating
information that starts automatically and is presented in parallel with other content, there is a
mechanism for the user to pause, stop, or hide it or to control the frequency of the update
unless the auto-updating is part of an activity where it is essential.
2.26 Web pages do not contain anything that flashes more than three times in any one second
period, or the flash is below the general flash and red flash thresholds.
2.27 A mechanism is available to bypass blocks of content that are repeated on multiple Web
pages.
2.28 Web pages/app screens have titles that describe topic or purpose.
2.29 If a Web page can be navigated sequentially and the navigation sequences affect meaning
or operation, focusable components receive focus in an order that preserves meaning and
operability.
2.30 The purpose of each link can be determined from the link text alone or from the link text
together with its programmatically determined link context, except where the purpose of the
link would be ambiguous to users in general.
2.31 More than one way is available to locate a web page within a set of web pages except
where the web page is the result of, or a step in, a process.
2.32 Headings and labels describe topic or purpose.
2.33 Any keyboard operable user interface has a mode of operation where the keyboard focus
indicator is visible.
2.34 All functionality that uses multipoint or path-based gestures for operation can be operated
with a single pointer without a path-based gesture, unless a multipoint or path-based gesture
is essential.
2.35 For functionality that can be operated using a single pointer, at least one of the following
is true:

5
 a. No Down-Event: The down-event of the pointer is not used to execute any part of the
function
b. Abort or Undo: Completion of the function is on the up-event and a mechanism is
available to abort the function before completion or to undo the function after
completion
c. Up Reversal: The up-event reverses any outcome of the preceding down-event;
2.36 For user interface components with labels that include text or images of text, the name
contains the text that is presented visually.
2.37 Functionality that can be operated by device motion or user motion can also be operated
by user interface components and responding to the motion can be disabled to prevent
accidental actuation, except when the motion is used to operate functionality through an
accessibility supported interface
2.38 The default human language of each Web page can be programmatically determined.
2.39 The human language of each passage or phrase in the content can be programmatically
determined except for proper names, technical terms, words of indeterminate language and
words or phrases that have become part of the vernacular of the immediately surrounding
text.
2.40 When any user interface component receives focus, it does not initiate a change of
context.
2.41 Changing the setting of any user interface component does not automatically cause a
change of context unless the user has been advised of the behavior before using the
component.
2.42 Navigational mechanisms that are repeated on multiple Web pages within a set of Web
pages occur in the same relative order each time they are repeated, unless a change is
initiated by the user.
2.43 Components that have the same functionality within a set of Web pages are identified
consistently.
2.44 If an input error is automatically detected, the item that is in error is identified and the
error is described to the user in text.
2.45 Labels or instructions are provided when content requires user input.
2.46 If an input error is automatically detected and suggestions for correction are known, then
the suggestions are provided to the user, unless it would jeopardize the security or purpose of
the content.
2.47 For webpages that cause legal commitments or financial transactions for the user to
occur, that modify or delete user-controllable data in data storage systems, or that submit user
test responses, at least one of the following is true:
 Submissions are reversible;
 Data entered by the user is checked for input errors and the user is provided with an
opportunity to correct them; and
 A mechanism is available for reviewing, confirming, and correcting information before
finalizing the submission.

6
2.48 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 any IDs are unique, except where the specifications allow these features.
2.49 For all user interface components (including but not limited to form elements, links and
components generated by scripts), the name and role can be programmatically determined;
states, properties and values that can be set by the user can be programmatically set; and
notification of changes to these items is available to user agents, including assistive
technologies.
2.50 In content implemented using markup languages, status messages can be
programmatically determined through role or properties such that they can be presented to
the user by assistive technologies without receiving focus.

3. Cyber security: Guidelines and attributes

3.1 Website, web application, web portal should be Security Audited and an Audit Clearance
certificate has been issued by NIC/ STQC/ STQC empanelled laboratory/CERT-In
empanelled laboratory before hosting in production environment.
3.2 Hosting Environment should be secured for ensuring confidentiality, integrity and
availability (CIA).
3.3 Website should have Security Policy and Privacy Policy clearly defined and approved by
the government organization.
3.4 Website should have the following clearly defined policies and plans approved by the Web
Information Manager (WIM):
a. Copyright Policy
b. Content Contribution, Moderation & Approval (CMAP) policy
c. Content Archival (CAP) policy
d. Content Review (CRP) policy
e. Hyper linking Policy
f. Terms & Conditions
g. Website Monitoring Plan.
h. Privacy Policy
i. Contingency Management Plan
j. Security Policy
3.5 Documents/pages in multiple languages should be updated simultaneously.
3.6 Mechanism should be in place to ensure that there are no ‘broken links’ (internal as well as
external) or ‘Page not found’ errors.
3.7 There should be no links to ‘under construction’ pages.
3.8 Documents should be provided either in HTML or other accessible formats.
3.9 Website should be bilingual with a prominent language selection link and uses Unicode
characters.

7
 EXPERIMENT 2
Aim: Configuration and Administration Apache Web Server.
Steps to Install XAMPP on window:
1. In Web Browser, download XAMPP from ApacheFriend Website.

Figure 2.1 Different version of XAMPP for window

After the download of the XAMPP following setup will be shown of the screen:

8
 Figure 2.2 Setup - XAMPP
2. During the installation process, select the required and click the Next button.

Figure 2.3 Setup components

3. Choose the root directory path to set up the htdocs folder for our applications.

9
 Figure 2.4 Select the root directory

4. Select the language and click on next.

Figure 2.5 Select the language

5. After the installation process, click the Finish button of the XAMPP Setup wizard.

10
 Figure 2.6 XAMPP control panel
6. To start Apache and MySql, just click on the Start button on the control panel.

Figure 2.7 XAMPP control panel

Server request:

11
1. Open the web browser and type https://localhost//. If you are able to see the default page
for XAMPP, you have successfully installed your XAMPP Server.

Figure 2.8 XAMPP localhost dashboard

2. Open the web browser and type https://localhost//myadmin. It will provide the admin
window to the user.

Figure 2.9 localhost//myadmin

12
13