Accessibility audits & remediation
Accessibility audits that find the real blockers — then engineers who fix them
We test your site or app against WCAG 2.2 level AA with automated tooling, keyboard-only walkthroughs and real screen readers, then remediate in your codebase and keep it from regressing. Try the live sandbox below to see the same levers working on this very site.
Live accessibility sandbox
Change a setting and watch our real site respond
This is not a mockup — it is this website, running inside a scrollable frame. Every control below maps to a remediation we implement on client sites.
Scroll inside the frame to explore. Settings apply to the frame only — your own preferences stay untouched.
Roughly one in five Australians lives with disability, and accessibility obligations under the Disability Discrimination Act 1992 apply to websites, not just buildings. The controls above — contrast, text scaling, spacing, typeface, link cues, reduced motion — are the exact remediations we ship, and they benefit every visitor on a small screen in bright sunlight too.
How an audit runs
Six stages, each with an artefact you keep
01
Discovery and scope
We agree the templates and journeys that matter — home, search, product or service detail, forms, checkout or booking, authenticated dashboards, PDFs and email templates.
Output: A scoped template and journey list with an agreed conformance target.
02
Automated baseline
axe-core, Lighthouse and Pa11y run across every scoped template at three viewports, in both light and dark presentations, to capture machine-detectable failures.
Output: A raw defect register with WCAG success criterion references.
03
Manual and assistive-technology testing
Keyboard-only walkthroughs, NVDA and VoiceOver passes, 400% zoom reflow, reduced-motion and high-contrast modes, and form error recovery under real failure conditions.
Output: Annotated findings with screen recordings of each blocking issue.
04
Report and prioritised plan
Every finding is rated by user impact and effort, mapped to the exact success criterion, with the code-level fix described rather than hand-waved.
Output: A conformance report plus a remediation backlog ordered by impact per hour.
05
Remediation sprint
Our engineers implement fixes in your codebase — or pair with your developers — starting with anything that blocks a task outright.
Output: Merged fixes, regression notes and updated component documentation.
06
Verification and monitoring
We retest, publish your accessibility statement, and wire automated accessibility checks into CI so regressions are caught before release.
Output: A verification pass, published statement and ongoing quarterly review.
Use cases
What we actually find, and what changed afterwards
Five representative engagements. Every one started as a business problem — lost enquiries, abandoned carts, a tender at risk — not a compliance checkbox.
Professional services
A keyboard trap that hid the contact form
- Problem
- A Brisbane advisory firm had a cookie banner that captured focus and never released it. Keyboard and screen reader users could not reach the enquiry form at all — the firm's only conversion path.
- What we did
- We rebuilt the banner on an accessible dialog primitive with a focus trap that releases on dismiss, added a skip link, and restored a visible focus ring the previous theme had removed.
- Result
- Enquiry form reachable by keyboard in three key presses; form completions up 18%.
- 2.1.2 No keyboard trap
- 2.4.1 Bypass blocks
- 2.4.7 Focus visible
Online retail
Checkout errors nobody could hear
- Problem
- An e-commerce client showed validation errors as red text only, with no programmatic association. Screen reader users heard nothing and abandoned at payment.
- What we did
- Errors were connected to inputs with aria-describedby, announced through a live region, given an icon plus text, and the submit button stopped being disabled without explanation.
- Result
- Assisted-checkout support tickets dropped by a third; recorded abandonment fell 11%.
- 1.4.1 Use of colour
- 3.3.1 Error identification
- 3.3.3 Error suggestion
Healthcare
Booking flow unusable at 400% zoom
- Problem
- A clinic booking wizard used fixed pixel widths and a horizontal scroll trap, so low-vision patients zooming to 400% lost the date picker off-screen.
- What we did
- We moved the wizard to a reflowing single-column layout, replaced the custom date picker with a native-first accessible component, and raised tap targets to 44px.
- Result
- Online bookings from assistive-technology users tripled over the following quarter.
- 1.4.10 Reflow
- 1.4.4 Resize text
- 2.5.8 Target size (minimum)
Government tender
A conformance report that survived procurement
- Problem
- A supplier needed evidence of WCAG 2.2 AA conformance to stay in a state government tender, with two weeks before submission.
- What we did
- We ran a scoped audit across nine templates, remediated the twelve blocking findings ourselves, then issued an accessibility conformance report and published statement.
- Result
- Tender submitted on time with documented AA conformance and no accessibility findings.
- Conformance report
- Published statement
- Named feedback path
SaaS platform
Design-system fixes instead of page-by-page patching
- Problem
- A platform team was fixing the same contrast and focus defects on every new screen because the component library itself failed AA.
- What we did
- We repaired the tokens and primitives — contrast-safe palettes for both themes, focus rings, motion preferences — and added axe checks to CI on every pull request.
- Result
- 94 recurring defects closed by twelve component changes; new regressions blocked in CI.
- 1.4.3 Contrast (minimum)
- 2.3.3 Animation from interactions
- 4.1.2 Name, role, value
Engagements
Three ways to start, all fixed-scope
Accessibility snapshot
From $1,900
Automated and manual review of up to five templates with a prioritised findings list.
- axe-core, Lighthouse and Pa11y baseline
- Keyboard-only walkthrough
- Prioritised findings with WCAG references
- 60-minute walkthrough call
Full WCAG 2.2 AA audit
From $4,800
Our standard engagement for a marketing site or a transactional flow up to ten templates.
- Everything in the snapshot
- NVDA, VoiceOver and TalkBack testing
- 400% zoom, reduced motion and high-contrast passes
- Screen recordings of blocking issues
- Accessibility conformance report
Remediate and monitor
From $2,400/quarter
We implement the fixes, verify them, then keep accessibility from regressing.
- Engineer-led remediation sprints
- Verification retest and published statement
- Automated accessibility checks in CI
- Quarterly re-audit and reporting
Prices are indicative in AUD excluding GST and confirmed after scoping. Bundled with a managed agreement, quarterly re-audits are included at no extra cost.
Questions
Accessibility audit FAQs
Still unsure where you stand? Read our own accessibility statement and contrast checker, or see how this work sits alongside web development and digital marketing.
What standard do you audit against?
WCAG 2.2 level AA, which is the level referenced by the Australian Government Digital Service Standard and by the Disability Discrimination Act 1992 guidance from the Australian Human Rights Commission. We report level A, AA and, where relevant, AAA opportunities separately.
Is an automated scan enough?
No. Automated tooling reliably detects roughly a third of WCAG failures — contrast, missing names, invalid ARIA. Keyboard traps, reading order, focus management, meaningful alt text and error recovery need a human. Every audit we deliver pairs axe-core and Lighthouse scans with manual keyboard and screen reader testing.
Which assistive technologies do you test with?
NVDA and JAWS on Windows, VoiceOver on macOS and iOS, TalkBack on Android, keyboard-only navigation, 400% browser zoom, Windows High Contrast mode and voice control.
How long does an audit take?
A focused audit of up to 10 key templates is delivered in five to seven business days. Larger platforms and transactional flows are scoped by template count and journey complexity.
Can you fix the issues as well as find them?
Yes. Most clients take the audit and then a remediation sprint where our engineers implement the fixes in your codebase, followed by a verification pass and an accessibility statement you can publish.
Do you provide a VPAT or accessibility conformance report?
Yes. Where you are tendering for government or enterprise work we produce an accessibility conformance report and a published accessibility statement with a named contact and feedback path.
Request an accessibility audit
Tell us your site or app and we will come back with a scoped audit, a timeline, and the three things we would fix first.
Prefer to talk it through? Contact our team