What a findings report actually tells you

"Fix your accessibility" is not a plan. "Your appointment-request form has an unlabeled field that fails WCAG 1.3.1, and here's where" is. The difference between those two sentences is a findings report — and it's the thing that makes every later decision possible.

What's in it

A findings report is the evidence from assessing a representative sample of your pages against WCAG 2.1 AA — automated testing plus structured human review. For each barrier we find, the report names:

• The page or document where it appears
• What the issue is, in plain terms
• The specific WCAG success criterion it fails
• How serious it is — critical, serious, or moderate

It also states plainly what we could and couldn't assess — pages behind a login, third-party content you don't control — so the report never claims more than it checked.

Why the report comes first

You can't scope a remediation project you can't see. Accurate estimates — of cost, of time, of effort — depend on knowing the actual barriers: how many, how complex, spread across how many templates. A report turns "we should probably do something about accessibility" into a concrete, prioritized list. It's also your first piece of documentation, which matters if you're ever asked to demonstrate a good-faith effort.

The report is free, and it's yours. Whether you fix things internally, with your own developers, or with a remediation firm, you walk away knowing exactly what the work is.

The next step: what it costs to fix

Once you know what's broken, the natural next question is what remediation actually costs and how long it takes. Our remediation partner, ClearPath Access, published a detailed, honest breakdown — real ranges for audits, remediation, documentation, and ongoing monitoring. It's the best plain-English guide to budgeting we've seen.

But the sequence matters: get the report first, so the estimate is based on your actual site instead of a guess.