What Halo measures that other accessibility scanners don't

Side by side

What each scanner checks automatically

We checked each vendor's own public documentation. For tools built on axe-core, we also checked axe-core's published rule list: it has no rule for reflow, focus visible, focus not obscured or keyboard traps.

"Not documented" means the vendor's public documentation doesn't say. "Needs Review" means the tool hands the check to a person instead of measuring it. In fairness, most tools let you set a custom width and run another scan; none of the documentation we found says a tool runs six widths in one automated scan.

Only with Halo

What you get that other scanners don't give you

• Six screen widths in one scan

  Every page is loaded at 320, 375, 640, 768, 1024 and 1440 px. A layout that works on one phone but breaks on another, or on a tablet, is caught in the same scan.

• Measured, not flagged for review

  Contrast over gradients, layered backgrounds, modern color spaces and chart labels is measured to a ratio. Other engines mark these for a person to check.

• Text spacing actually applied

  Halo applies the WCAG 1.4.12 spacing settings and looks for clipped or overflowing text. Rule engines only look for inline spacing styles.

• A real keyboard walk

  Halo presses Tab through the page at phone and desktop widths and checks every stop: is focus visible, is it hidden under a sticky header, does it get stuck?

• A fix with every finding

  Each finding comes with its usual cause and the fix, from our knowledge graph, written in plain English.

• False alarms already filtered out

  Skip links mid-animation, embedded booking widgets, visually hidden text and stacked backgrounds are known look-alikes. Halo has learned them, so your report shows real issues.

• Search problems in the same pass

  Redirecting URLs, canonicals that point elsewhere and duplicate page titles are reported alongside the accessibility results.

• A person approves the work

  Every client scan and every new lesson is approved by our team before it runs or goes live.

We ran Halo on our own site first. Its first pass raised 159 flags: 34 were real issues, which we fixed, and the rest were false alarms that became lessons, so they aren't raised again.

See it on your own site

Run the free accessibility scanner. Halo checks your page at all six widths alongside the axe-core results.