The page now leads with adding a picture, then its answer: how wide to print it to scan from a table, for every picture whose code's version a scanner reported or the checks estimate. Below, as the evidence, all 6,499 codes sit on one scale from easy to hard.
The pixel check now takes its limits from the grid behind the print widths, in its good-light scene, by the same rule as the other checks: Fine from 4.45 camera pixels per square at every version, and a Problem limit that rises with the version.
At a slant, or on a can or bottle, the width grows so that the squares the phone sees narrowest keep the need. No width is given turned past 55°, for a code wider than the diameter over 1.2, or where the code and its margin, turned, would no longer fit the camera's view.
Behind the + under the answer, What a phone sees draws your picture as a phone's scanner would get it, printed at the width worked out and seen from its distance. It is an illustration, not a scan.
A test sheet, to pri…
7 days ago
Fix small issues: shown-number statuses, hoverable tips, right-pile line
Each picture check now takes its status from the number the page shows, so one shown number never has two statuses. Hover tips stay while the pointer is on them. A redrawn section brings its heading into view. A picture none of the five scanners read is described by the measured codes like it. The page's remaining sentences come from copy.json. Try again sits under a failed row's text. The reading code is split into smaller modules, unchanged.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HykRoFZnnb98KRf6Xxomka
Each picture now gets a level (Easy, Everyday, Tough or Advanced) with a confidence, and checks of what the picture shows, with explanations and advice.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HykRoFZnnb98KRf6Xxomka