How a JBMD Accessibility Audit Works

The first look

We start with a quick pass over your site and flag the accessibility barriers we can see without digging.

• A menu you can't open by keyboard
• Images carrying no description
• Text at a contrast ratio that fails on sight
• Form fields with no label attached
• A focus outline that's been styled away

This isn't the full report. It's enough to tell you honestly whether there's something here worth pursuing. If your site is genuinely in decent shape, we'll say so.

See how the two lanes fit into one audit

We reach out with what we found

We get in touch with the highlights in plain language. On the accessibility side that means describing what a real visitor runs into, not reciting criterion numbers at you. A screen reader announcing your main call to action as link is a sentence you can act on. A 1.4.3 failure is not. You get an honest picture of where your site sits, and you decide whether to go further.

If you want to proceed, we walk you through the full audit

We explain exactly what the in depth accessibility work covers before you pay for anything.

• Your pages get crawled and captured at desktop, tablet and mobile sizes
• Automated checks clear the machine detectable issues as a first pass
• We work the WCAG 2.2 Level A and AA criteria by hand on real pages, with a screen reader and a keyboard

Most of those criteria turn on judgement a scanner can't make. If you're in Ontario at 50 or more employees, WCAG 2.0 Level AA is the level the AODA web standard names, and it sits inside what we check. We'll show you our own site's audit PDF first, so you can see the format and the depth.

See how deep the audit actually goes

You're sent an invoice

Once you're ready to move ahead, we send an invoice for the audit. The full work begins once it's paid. Simple and up front, so everyone knows where they stand.

You receive two documents

Two copies, written for two different readers. An Overview, a plain language summary you can read or hand to a decision maker, and a Developer Audit, the full technical breakdown. Every accessibility finding names:

• The success criterion it failed
• The pages it appears on
• What a person using a keyboard or a screen reader actually hits
• How to fix it, with screenshots and marked up drawings
• Fix code in HTML, CSS and JavaScript

Privacy findings land in the same two documents, tagged to their own lane, so you get one report rather than two.

Optional: we fix it for you

If you'd rather we made the changes than hand the report to your own team, we can. On the accessibility side that's the remediation work itself.

• Making every control reachable and operable by keyboard
• Giving controls proper names and roles
• Restoring a visible focus state
• Fixing contrast
• Rebuilding heading and landmark structure so assistive tech can navigate the page

We'll ask for access to your site's code so the estimate is based on what's actually there rather than a guess. Once you approve the rates, we start. Plenty of owners hand the report to their own developer instead, which is a perfectly good outcome. It's written so someone who isn't us can work from it.