Polish check
Paste a page’s address. In about ten seconds you see what a script can measure about its polish (contrast, type, tap targets, control edges, motion) drawn on the page itself.
What it checks
- Contrast below AA
- Darken the text or lighten what is behind it, to 4.5:1 (3:1 for large text).
- Text under 12 px
- Nothing on a screen reads below 12 px. Set it to 12 px or more.
- Target under 44 px
- Make the box a finger hits at least 44 by 44 px, with padding or a larger hit area.
- Faint control edge
- An input’s or an outlined button’s edge needs 3:1 against what is behind it; aim for 3.4.
- Sentences under 16 px
- Set sentences at 16 px or more; keep smaller sizes for short labels.
- Text faded with opacity
- Give the text its own colour instead of fading it, so its contrast is what it looks like.
- transition: all
- List the properties that change, such as opacity and transform: `all` animates layout too.
- Text on a half pixel
- Round the translate to whole pixels: text moved by a fraction renders soft.
- Orphan in a heading
- Add `text-wrap: balance` so the heading’s lines even out.
- Contrast on the line
- It passes by less than 0.4. The next background or theme can push it under: aim 0.4 higher.
What it keeps
Nothing. The page is opened once, in a browser on our server, as anyone on the internet would see it. The address, the page and the results are gone when the answer is sent.
What it can’t see
Motion as it feels, every state a component can be in, keyboard flow, and which fixes are worth the most. That is the Polish Audit.
Behind a login
Run the same check in your own browser: drag this to your bookmarks bar, then open it on any page, signed in or not. Nothing leaves your browser.