← ClaudeAtlas

indian-gov-web-uilisted

Use when building or reviewing a UI for an Indian government website, portal, or admin panel — covers GIGW 3.0, DBIM v3.0, UX4G, and the WCAG criteria that are statutory in India. Triggers include gov.in sites, state government portals, PSU/महामंडळ sites, bilingual Hindi/Marathi/regional government content, and staff-facing admin panels for government content.
Yashraj00700/indian-gov-ui-skills · ★ 2 · Web & Frontend · score 65
Install: claude install-skill Yashraj00700/indian-gov-ui-skills
# Indian Government Web UI ## Overview Indian government web UI is governed by three documents that do different jobs: | Document | What it governs | Binding? | |---|---|---| | **GIGW 3.0** | *Required content and behaviour* — what must be on a page | **Mandatory** for Central + State government sites at any level. ⚠️ **Intranet applications are "recommended", not mandated** (see `gigw-requirements.md` Scope) — but that is not a WCAG exemption | | **DBIM v3.0** | *Visual identity* — palette, type scale, header/footer/homepage anatomy | Written for **Government of India** platforms. **Voluntary** for a state government or state corporation | | **UX4G** | *Component library* — v2 is a Bootstrap 5 fork, v3 is a rewrite | **Advisory only.** Binds solely when written into a procurement SoW/TOR. No official React package exists | **Core principle:** GIGW tells you what must exist, DBIM tells you what it should look like, UX4G gives you components. Only WCAG will get you fined. ### Which WCAG version are you actually building to? Four different standards get cited in this space. Resolve it explicitly at project start: | Source | Says | |---|---| | **GIGW 3.0 §5.2** | WCAG **2.1** Level AA | | ***Pragya Prasun* direction (ix)** | WCAG **2.0** Level AA | | SC 2.5.7 (dragging) | WCAG **2.2** — *not in force in India* | | Draft RPwD Rules 2026 | **IS 17802** Parts 1 & 2 | **Recommended default: build to WCAG 2.1 AA.** It is what GIGW 3.0 adopts, it is a strict superset of the 2.