Governance
How UX4G is governed, how components mature, how any team can contribute, and what conformance means — decisions made in the open, documented, and traceable.
How it's governed
A small core team stewards the system; decisions are made in the open and documented, so anyone can follow how and why the system changes.
Open by default
Decisions, proposals, and the roadmap happen in the open on GitHub.
Accessible by default
WCAG 2.1 AA is the floor — verified before anything ships.
Built by the community
Any government team can propose, contribute, and be credited.
Who owns it, and how decisions get made
The UX4G core team holds final authority across three areas. Proposals are raised as GitHub issues, discussed openly, reviewed by the relevant leads, and the outcome is recorded — so there's always a traceable rationale.
Component lifecycle
Every component carries a maturity label so teams know what they can rely on. Components advance only after accessibility and real-world testing, and nothing is removed without a migration path and advance notice.
Early testing — breaking changes expected. Not for production.
Feature-complete, being tested with departments. Use with care.
Stable and recommended for all government services.
Scheduled for removal — a replacement and migration path exist.
What teams say
Designers, developers, and researchers across India share what changed after adopting the system.
We were about to build a custom OTP flow for our grievance portal. Found the pattern in UX4G, adapted it in a day — saved us at least two weeks.
The accessibility checklist alone changed how our team works. We used to ship and patch. Now we test with NVDA and Hindi voiceover before review.
Our portal lists rural housing schemes across eight districts. Borrowing the status-pipeline component meant citizens see exactly where their application stands.
Solutions from the community
Service-specific components, patterns, and flows built by government teams and shared for others to adapt — with Figma files, code, or documentation.
Pension Eligibility Stepper
Ministry of Rural Development
Multilingual Form Reset
Income Tax Department
Doorstep Service Tracker
Department of Posts
Aadhaar-Seed Reminder
UIDAI · Ministry of Electronics & IT
Crop Status Pipeline
Ministry of Agriculture & Farmers' Welfare
Grievance Escalation Map
Department of Administrative Reforms
Contribute
Solved a problem other teams will face, or shipped a portal worth showing? Add it. Gentle gatekeeping — every listing here is one you can trust.
What makes a good contribution
Conformance
Government services are expected to conform to UX4G — consistent components, design tokens, and WCAG 2.1 AA accessibility across every citizen-facing flow.
Conformance is about better services for citizens, not box-ticking. Teams working toward full adoption get priority support and migration help — reach the core team at support.ux4g@digitalindia.gov.in.