Verify
Checked before anyone sees it.
Every screen, every pack, light and dark, phone and desktop. Then an agent tries to finish the task by name alone.
13 design systems you already know
12 templates to start from
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Open it in the gallery
Checked before anyone sees it.
- Every label read aloud
- Contrast 4.5:1 and up
- Only allowed actions
- Every value bound to your data
- An agent finished the task
- renders checked across the examples and four products
- 4,680
- tasks finished by agents, by name alone
- 936 / 936
- deliberately broken screens caught
- 20 / 20
Four layers of checks.
- 01
Document
Schema, references, one primary action per view, data bindings, the pattern’s rules, allowed actions, labels that say what happens.
- 02
Rendered
Headless Chromium in each pack, mode and width: axe-core WCAG 2.2 AA, contrast, overflow, target size, runtime errors.
- 03
Agent
Scripted tasks through the accessibility tree only. The product must receive the expected action.
- 04
Consistency
Two generations of the same ask, compared.
Twenty broken screens. Twenty caught.
Two primary actions, a destructive action outside a confirmation, a hard-coded balance, an image without alt text, a required field removed so the task can’t be done, and fifteen more.
The verifierpolyxd-verify ./screens schema ........... pass patterns ......... pass actions .......... pass axe, contrast .... pass agent tasks ...... pass