How to use
- Start from one token-ready base color and choose the same target you would use for preview or export.
- Use the issue list to spot weak contrast pairs, duplicate roles, and token pairs that look too close to keep separate.
- If the audit still looks acceptable, move next to Color Token Export. If the issue list feels too abstract, step back once to Color Token Preview.
Wave 56 expansion
Audit token consistency before handoff
This page answers one narrower question after preview: is the token set internally consistent enough to export, or are there obvious duplicates and weak pairs you should fix first?
How to choose between nearby pages
Use Accessible Color Palette while the role assignment itself is still changing. Use Color Token Preview when you still need a browser-side UI sign-off. Use this page after preview, when the remaining question is whether the token set is internally consistent enough to export. Use Color Token Diff after the audit if the next question is how the next token set differs from the current one. Use Color Token Export only after the audit is acceptable enough for code handoff.
FAQ
What does this page audit?
It audits one generated token set and flags weak contrast pairs, exact duplicate roles, and overly similar token pairs before export.
When should I use this instead of Color Token Preview?
Use Color Token Preview when you still need a browser-side UI sign-off. Use this page when the remaining question is whether the token set is internally consistent enough to export.
When should I use this instead of Color Token Export?
Use this page before export when you want one quantitative consistency gate. Use Color Token Export after the audit is acceptable and the next job is copying CSS vars or JSON tokens.
Does this replace a full design-system review?
No. It is a lightweight consistency check only and not a replacement for full product or brand review.