What happens when you type your address

It reads your site like a careful customer

The audit follows the links on your site and reads each page's text — the policies, the product descriptions, the small print. It notices what a person would: a shipping policy naming another company, two prices for the same thing, a legal page that still says Lorem ipsum.

It checks the links it finds, inside your site and out, and reports only the ones that fail.

It opens your pages in a real browser, and looks at them

Many sites build their pages in the browser, so the HTML your server sends is not what a visitor sees. The audit opens pages in Chrome and looks at the screenshot — which is how it catches a product photo that contradicts the text beside it.

Cookie banners are hidden before a screenshot is taken, never clicked, so nothing is accepted on your behalf.

It tries to prove itself wrong before it tells you anything

Every problem the auditor reports goes to a second agent whose only job is to disprove it. It re-opens every address and rejects the claim if the page does not say what it says, if the thing said to be missing is there, or if it is normal behaviour rather than a defect.

Then code has the last word: a quote must be on a page we read, a status must be one a request returned, and every count is made by code from what was recorded.

One document, for you and your developer

A verdict on the first page, in one sentence. Then one page per problem: what your site does, the evidence beside it, why it matters, and what to ask for. A short plan points back at the findings and estimates the effort of each.

Every term is explained once, where it is first used, so the report can be forwarded as it is.

It says what it could not see

We read your site from outside, as a visitor does: nothing behind a login, no payments, and nothing that would change your site. Every report ends with what we could not measure and why.

Every request names us, so your server's logs show who called.

Read what we cannot see