Analysis
The example · After the capture, Analysis scored Northwind 86 for consistency and 72 for accessibility, and ranked 14 fixes.
Analysis runs after every capture. It is the first thing you see once a capture finishes.
Scores
| Score | Measures | Goes up when |
|---|---|---|
| Consistency | How much of the site uses your tokens and components | Off-system values are mapped, duplicates merged |
| Accessibility | Contrast, labels, focus order, tap sizes | Failures are fixed |
| Match to main | How closely the live site matches main | The site ships what main says |
Each is 0–100 and shows its change since the last capture.
Found and gaps
What the capture read — pages, components, tokens, icons, links, roles — and what is missing: states never shown, values that match no token, failures.
Fix first
Fixes are ranked by how many users would see them and how many places they touch. Open one for the detail.
- Fix in my draft makes the changes for you; they go to your draft like any edit, to review and commit.
- Ignore hides a finding until something about it changes.
- A fix marked with ✦ is written by AI and uses one AI action.
Free month and Team
| Free month | Team | |
|---|---|---|
| Scores, found and gaps | ||
| Fix first and finding detail | — | |
| Fix in my draft | — | |
| AI analysis | — | 1 AI action per capture |
Was this page helpful?
Yes
No
Updated Oct 22, 2026