OAKMONT Inspector

Check any page in the browser you are already using - including the ones behind a login that no external scanner can reach.

Most accessibility checkers read a page from outside. That rules out everything that matters: the account area, the intranet, the staging site behind basic auth, the third step of a checkout. OAKMONT Inspector runs inside the browser you are already signed in to, so it checks the pages your customers actually use. WHAT IT MEASURES, RATHER THAN READS - Contrast after compositing every translucent layer between the text and the page, which is what the eye receives and what a stylesheet check misses. - Focus visibility by focusing each element and comparing what the browser paints. - Reflow by zooming the tab to the width the criterion names, not by reading media queries. - Text spacing by applying the 1.4.12 values and measuring what stops fitting. - Keyboard behaviour with real key presses: Enter and Escape sent through the browser, not synthetic events a page can tell apart from a person. - 51 rules in all, including web components: it looks inside open shadow roots and every frame, because a checkout is usually a payment iframe inside a page. WHAT IT WILL NOT DO It will not tell you a page is compliant. 27 of the 55 A and AA criteria cannot be decided by any tool, and the Coverage tab names every one of them rather than quietly leaving them out of a score. A green result here is the automatic half, and it says so. WHAT YOU GET BACK - The fault first, in one line. The reasoning is behind a question mark, one press away. - The corrected value, not just the complaint: the nearest colour that passes on the background actually behind the text, the scroll margin measured from the bar doing the obscuring. - A report you can hand over, with screenshots, written on your machine. - Optionally, with an OAKMONT account: a signed receipt at a public address anybody can open, and the record of what this page scored the last five times somebody looked. PRIVACY Nothing leaves your browser unless you press Send. Checking is entirely local, and so is every export. When you do send, it carries the address of the page, its title, and a list of rule codes with a CSS path for each. Never a cookie, a token, a password, the page source, or a screenshot. OAKMONT Technologies LLC - https://oakmonttechnologies.com