Who builds this

I'm a full-stack developer. I have been building web applications for more than 15 years, including several years running my own development agency, fullcycle.io.

I write the scanner, the guides on this site and the research reports. When you email hello@accessibilityscanner.app, I read it.

It loads a page in a real browser, scrolls it so lazy-loaded content renders, and runs axe-core, Deque's open-source engine, against WCAG 2.2 Level A and AA. Every finding names the element and the success criterion it fails.

Two checks go beyond axe. Axe leaves text over gradients, background images and translucent overlays as "needs review", so the scanner measures the worst case under the text and returns a pass or fail. Axe also never focuses anything, so the scanner tabs to each control and measures contrast in the focused state.

The same engine runs as a Chrome extension, a CLI, a GitHub Action and an MCP server. They are listed on the integrations page.

An automated scan covers roughly a third of WCAG's success criteria. It can tell you a line of text fails 4.5:1. It cannot tell you whether an image's alt text describes the image, or whether a checkout makes sense to someone using a screen reader.

So a clean scan is never reported as "compliant", and anything the engine cannot measure stays on a review list instead of being counted as a pass. This is not an overlay and adds nothing to your site. The overlay guide explains why that matters.

The sector reports on online stores, hospitals, federal government and banks come from scanning 342 real homepages with the same engine you use here. They report aggregate figures only and name no organisation. Each report ends with its sample, exclusions and limits, and the cross-industry comparison puts them side by side.

If a guide gets something wrong, email hello@accessibilityscanner.app and I'll fix it. Each guide shows the date it was last changed.

Elsewhere: LinkedIn, GitHub and dev.to.