Government websites are where citizens pay taxes, apply for certificates, check benefits and file grievances. When those sites are slow, confusing or inaccessible, the cost is not a lost sale. It is a person unable to reach a public service.

India addresses this through the Guidelines for Indian Government Websites, known as GIGW. The current version, GIGW 3.0, raises the bar on usability, accessibility and security, and it now covers mobile apps as well. This guide explains what GIGW 3.0 is, what it requires and how teams can approach compliance. It is general information, so always check the official guidelines and your department’s instructions.

What Is GIGW?

GIGW is a set of standards for building and managing government websites and apps in India. The National Informatics Centre (NIC) first formulated the guidelines in 2009, and GIGW 2.0 later took account of international standards such as those from the W3C and added guidance on mobile apps. The latest edition, GIGW 3.0, was released in 2023. Official documents from the STQC Directorate place the release in March 2023.

The aim is consistency and quality across thousands of government digital properties. The guidelines are meant to make government websites and apps user-centric, user-friendly and secure, and they apply to central and state governments, including district administrations and local governments.

The UUU Trilogy

GIGW is built around three ideas, often called the UUU trilogy: usability, user-centricity and universal accessibility. That framing matters for design teams because it treats UX as a compliance concern, not a polish step.

What Is New in GIGW 3.0?

The main emphasis of GIGW 3.0 is on improving the user interface and user experience of websites and apps, supported by user-centric information architecture that eases the user journey and delivers content according to user needs. Several other changes stand out:

• Apps are now explicit. The title became “Guidelines for Indian Government Websites and Apps,” though the GIGW acronym was kept, with the “W” now standing for websites and apps.
• Stronger accessibility. The current version ensures conformity with WCAG 2.1 Level AA.
• Better mobile guidance. It significantly expands guidance on app accessibility and usability, including how organisations can make use of public digital infrastructure.
• Language inclusion. Websites are expected to offer content in multiple Indian languages, so that non-English speakers and rural users are included.

How GIGW 3.0 Is Structured

Commentary on the guidelines describes 88 mandatory guidelines across domains that include Quality (25 guidelines), Accessibility (50 guidelines aligned with WCAG 2.1) and Cybersecurity (3 guidelines). Lifecycle management forms a further area, covering how sites are maintained over time. Treat the official document as the authority on exact numbering and wording, since secondary summaries can differ.

Quality

Covers content, design and consistency. Reporting on the guidelines notes a mobile-first approach with responsive layouts, faster load times and clear navigation menus. In practice this means consistent templates, current content, working links, clear contact details and policy pages.

Accessibility

The largest domain, and the one most affected by design decisions. It follows WCAG 2.1 AA, so it covers text alternatives, contrast, keyboard operation, form labels, error handling, captions, resizable text and predictable navigation. Our guide to inclusivity and accessibility in experience design explains the principles behind these requirements.

Cybersecurity

A short but critical set of requirements for protecting data and services. Security is typically assessed separately from design, but UX teams should avoid patterns that undermine it, such as exposing sensitive data in URLs or weakening authentication for convenience.

Lifecycle management

Government sites often decay: outdated notices, broken documents, orphaned pages. Lifecycle expectations cover content ownership, review cycles, archiving and keeping platforms current.

Who Needs to Comply?

GIGW covers both websites and mobile apps, and all websites and apps owned by government organisations are expected to comply. If you are an agency or vendor building for a department, the requirements flow to you through the contract. India’s disability rights law also treats accessibility of information and communication technology as a legal expectation, so GIGW compliance supports obligations beyond the guidelines themselves. vikaspedia

Organisations are expected to assess existing sites and apps against GIGW 3.0, identify gaps and draw up time-bound plans to reach conformity, and projects still at the design or build stage should be reviewed against it as well. Many older properties will need real investment: coverage of the guidelines notes that legacy systems will often require major overhauls, along with training, audits and funding. indiadigit

Certification and Auditing

Conformity is assessed through audits and certification, typically through the STQC Directorate under MeitY. Teams usually prepare for this by running an internal review first, fixing issues and then commissioning a formal audit. The process and fees can change, so confirm current procedures with STQC or the relevant NIC team.

A Practical Approach to GIGW 3.0 Compliance

1. Inventory what you own

List every website, portal, web application and mobile app, along with owners, platforms and hosting. Many departments discover forgotten microsites during this step.

2. Run a gap assessment

Test against GIGW 3.0 using automated tools, manual checks, keyboard testing and screen readers. Automated scans catch only part of the accessibility picture, so human review is essential. A structured approach like identifying design flaws with a UX audit helps teams record each issue with its location, severity and recommended fix.

3. Fix the information architecture first

GIGW 3.0 puts user-centric structure at the center. Group services by what citizens want to do, not by departmental org charts, and make search, navigation and labels predictable. Strong information architecture reduces both usability problems and support load.

4. Build accessibility into components

Fix shared templates and components once: accessible forms, focus states, headings, tables, date pickers, document links and modals. Fixing a component fixes every page that uses it.

5. Handle documents, media and languages

Government sites carry many PDFs, scanned notices and videos. Provide accessible versions, tagged PDFs, captions and transcripts. Plan multilingual content properly, including correct language attributes and fonts that render Indian scripts reliably.

6. Design for low bandwidth and basic devices

Many users reach services on entry-level phones and slow connections. Keep pages light, avoid heavy scripts and test on real devices.

7. Test with real users

Include citizens with disabilities, older users and people with limited digital literacy in usability sessions, not only internal staff.

8. Plan ownership and maintenance

Assign content owners, set review dates, remove outdated material and schedule recurring audits. Compliance that is not maintained expires.

Common Mistakes to Avoid

• Treating GIGW as a one-time certificate rather than an ongoing practice
• Relying only on automated accessibility scans
• Publishing scanned, untagged PDFs as the main way to deliver information
• Ignoring mobile apps, now explicitly in scope
• Organizing navigation by department structure instead of citizen tasks
• Skipping Indian-language content or testing it poorly
• Leaving outdated content live, with broken links and expired notices
• Fixing pages individually instead of fixing shared components
• Starting late, leaving no time for fixes before an audit

A Quick Checklist

• Do we have a full inventory of sites and apps?
• Have we run a gap assessment against GIGW 3.0, including WCAG 2.1 AA?
• Is navigation organized around citizen tasks?
• Are forms, documents and media accessible?
• Do we support the required languages and low-bandwidth use?
• Are security requirements reviewed alongside design?
• Do we have content owners, review cycles and an audit plan?

Bringing It All Together

GIGW 3.0 asks government digital teams to deliver sites and apps that are usable, secure and accessible to every citizen. The guidance puts UX, information architecture and WCAG 2.1 AA at the center, which makes design teams key partners in compliance, not bystanders.

Begin with an honest inventory and one important citizen journey. Test it with a keyboard, a screen reader and a mid-range phone, and note every barrier. That list is the start of a time-bound implementation plan.

If you are building or modernizing digital services for public bodies, see how we approach government and public sector projects, or work with a trusted UI UX design company in Bangalore that can help you audit, redesign and test experiences that serve every citizen.