The Web HIG
A practical standard for how web interfaces should behave.
The Web HIG gives teams a shared set of rules for usable, accessible, responsive, performant, predictable, and safe web applications.
Design systems define what your UI looks like.
The Web HIG defines how it behaves.
It is not a component library, CSS framework, or visual theme. Keep your existing stack and use HIG as a practical behavior and quality contract. Why it exists →
New to The Web HIG?
Start here if you are seeing the project for the first time. The short version: HIG helps you decide what should happen around your components when real users load, navigate, submit, search, fail, recover, resize, or delete something.
What it is
A vendor-neutral, versioned web interface standard for behavior, interface states, accessibility, performance, security UX, and AI-assisted implementation.
What it is not
Not a component library, Figma kit, CSS framework, brand system, or replacement for WCAG, HTML, CSS, ARIA, or your design system.
When to use it
Use it while building, reviewing, auditing, or asking an AI coding agent to change a web interface consistently.
Choose your first step
New in v1.18.0: agent consumption metadata
Accessibility, forms, motion, and performance rules now carry maturity, a browser target, a fallback, automated checks, manual checks, and a source date. Audits judge the outcome. A modern API is not a pass. image-animation stays an experimental technique and is not a conformance result.
Core Web Vitals thresholds and WCAG mappings are unchanged. The standard still has 98 Quick imperatives and 76 stable rule IDs.
Read the v1.18.0 release notes → · Content / Marketing examples from v1.15.0
Companion: Design Decision Method
You can use WebHIG with your existing design process. WebHIG and Design Decision Method (DDM) help with different parts of the work, and each stands on its own.
| Name | What it helps you do | Example |
|---|---|---|
| WebHIG | Build interfaces that behave clearly, consistently and accessibly | Make errors understandable and preserve entered information when saving fails |
| Design Decision Method (DDM) | Choose an interface that fits the people and task | Decide whether a task needs one form or a step-by-step flow |
If you also want help choosing layouts, navigation and interaction patterns, DDM gives you a structured way to make those decisions. DDM is optional.
Explore the documentation
The site is split into focused pages so first-time visitors can start small and go deeper only when they need more detail.
Step 1
Understand
Plain-language overview: what HIG is, what it is not, why it exists, and where it fits in your stack.
Open Understand →Step 2
Adopt
Start with one file, then pin the standard, run the installer, map routes, and add checks when your team is ready.
Start adopting →Step 3
AI & agents
Tell Cursor, Copilot, Claude, or another coding agent which HIG layer to follow without loading the full spec every time.
Use with AI →Lookup
Reference
Archetypes, rule ID prefixes, validation, spec index, glossary, and full FAQ.
Browse reference →One standard. Three levels.
Progressive disclosure — load only what you need. Pin HIG-QUICK instead of the full specification.
Essential rules (summary) 10 governance layers Loading model for agents
Common questions
Where do I start?
Start with New to The Web HIG?, then read HIG-QUICK.md. It is the everyday onboarding path and takes about five minutes.
Is this a component library?
No. You keep your design system and stack; the HIG defines behavior, states, accessibility, performance, and security UX.