Practical checks for people shipping websites, plus measured findings from real browsers. Method and raw numbers included, especially when they make our own product look less impressive.
A page loading is not a release test. This is the browser checklist for the week before client handoff: the money path, keyboard use, form failures, real content, mobile layout, browser errors, page basics, and evidence another developer can retest.
Our checker called a major Danish retailer clean because it was measuring
the consent overlay. It also missed modern click handlers that were attached
with addEventListener.
Both defects were in our own tool. The article includes the reproduction steps and the changes that made the browser result more honest.
One page from each of 27 Danish and Swedish shops, loaded in a real browser and audited the way a visitor's machine would. Every finding verified against the live DOM.
The result that matters is not the total. It is that four sites had a control a keyboard user simply cannot operate. axe-core alone found 92% of everything we found, which is the number that undercuts our own pitch.
axe-core is good software and it runs inside our own tool. But it reads the accessibility tree, and some failures are invisible from there.
A <div> with an onclick and a pointer cursor looks and
behaves like a button for anyone with a mouse, while being absent from the tab order and
deaf to Enter and Space. Detecting that means comparing computed styles, event handlers
and focusability together. That is a different question from the one a rules
engine over the accessibility tree is asking.
The Nexaaly Critical-Flow Bug Hunt tests one authorized signup, onboarding, checkout, upgrade, booking, invitation, or similar flow. You receive reproduced findings, exact steps, severity, browser evidence, and one retest for EUR 49 excluding VAT where applicable.
Review the exact scopeWant the method first? Use the 90-minute critical-flow checklist or see the controlled sample report.