A website accessibility audit should tell you who can't use your site, and why. A scanner catches what a machine can see. Then a person tests your site the way your visitors do. That means by keyboard, by screen reader and against the WCAG 2.2 AA contrast ratios. You get a findings list ranked by who each problem stops.
Partner badges you can look up, numbers straight from client dashboards, and the businesses whose websites we've built. Here's the scoreboard so far.
What we do
“The entire process was seamless, easy, and incredibly user-friendly. They were patient and flexible with all the changes and back-and-forth... Most importantly, they absolutely nailed the brief.”
5 stars Google review
What is included
Four rules every audit follows. Together they turn the report into a to-do list your developer can start on straight away.
The automated scan clears the obvious in bulk. That leaves the manual hours for what only a person can judge.
How a build runsWe walk the paths a visitor has to finish with a keyboard and nothing else. That means the enquiry, the booking and the checkout.
See the workEvery finding names the WCAG 2.2 success criterion it fails. The evidence sits right beside it.
The proof we showEach finding carries the element's source and the change that would fix it. It can go straight into a ticket.
Questions people askThe argument
A scanner, then a person
Keyboard, screen reader and contrast, by hand.
A scanner and a PDF
Only what a machine can detect.
WCAG 2.2 AA, criterion by criterion
Every finding cites its success criterion.
A score out of 100
A number with no criterion behind it.
Ranked by who it blocks
A form nobody can tab through comes first.
Listed in page order
Hundreds of rows, all the same weight.
Steps anyone can repeat
Page, element, steps and the expected result.
A selector and a rule name
Your developer works out the rest.
Where the site stands, plainly
An audit reports conformance. It can't grant it.
A compliance badge
A certificate nobody is entitled to issue.
How it runs
You see the page plan before design starts, and the design before we build. So there are no nasty surprises at the end.
Scope
We agree which templates and key paths get tested. A 400-page site is usually a dozen templates repeated, so the quote follows the templates.
What we deliver
What do people search before they call you?
Automated scan
Every page in scope goes through an automated scan. It catches missing labels, broken ARIA and contrast failures in bulk.
What we deliver
Monthly searches
Manual testing
Then a person works each key path by keyboard and screen reader. They measure contrast where a scanner can't, such as text over images and on hover.
What we deliver
Sentient / Inter
14.05:1Report
We write up each finding with its criterion, the evidence and a suggested fix. Then we rank them by how many people each one stops.
What we deliver
Walkthrough
We take your team through the report and answer the questions it raises. Together we agree which findings get fixed first, and by whom.
What we deliver
Baseline recorded
14 OctThe long read
An audit is a measurement. It measures some things well. Others it leaves to the people who fix the site.
An automated tool reads the code and checks it against rules. It's fast, thorough and honest about what it finds.
It can tell you a button has no name. It can't tell you whether the order makes sense when you tab through the page. Nor can it judge whether an image description says anything useful.
That judgement takes a person with a keyboard and a screen reader. It's where most of the audit time goes.
Illustrative: the rough shape of the split, not a measurement. Every site in scope is tested both ways.
A report with 300 findings sounds thorough. Usually it's 10 problems repeated across 30 templates, and the count is the least useful number in it.
So we group findings by pattern and rank them by who they stop. An unlabelled field on the enquiry form outranks a decorative image on the blog.
That order decides whether a report gets fixed or gets filed.
There's no official WCAG certificate, and there's no certificate an audit can hand you that makes a site compliant.
What you get is an honest, dated record. It shows which success criteria the site meets on the day we test it, which it fails, and the evidence for each.
That record is what your accessibility statement should rest on. It's also the baseline every later change gets measured against.
We report, we suggest the fix, and we show the markup where it helps. But fixing is a separate job, and we keep it separate on purpose so the report stays an honest measurement.
If your own developers are doing the work, we write the report for them. If you'd rather we did it, that's our accessibility fixes service, and it starts from this report.
Case studies
Speech Clinic
A search-led structure giving each therapy and each mobile service area its own page to land on.
Scope of work
MedPrescribe
An e-prescribing platform positioned as a product, automating booking through to delivery.
Scope of work
First Class First Aid
A booking site built around the codes employers send, not the course names.
Scope of work
Ovaya
An at-home fertility treatment page answering what arrives, when, and who watches each cycle.
Scope of work
Full Body MRI
A whole-body screening scan surfaced by the organ or condition people actually search for.
Scope of work
Search proof
Shopify Partner
Shopify stores built so search can read the whole catalogue, with tracking on every sale.
Google Partner
Partner status you can look up in Google's own directory. Every result above comes with the screenshot behind it.
Where we work
Engagements
Find the patterns
For a site built from a handful of templates, or a new site before launch. Each template gets tested once, in depth.
Test what people finish
For a site where enquiries, bookings or sales have to work for everyone who arrives.
Tools and integrations
We pick the platform that suits your business. Then we connect the site to your booking system, your CRM and your ad accounts, so every enquiry lands where your team already works.
Client results
“Up until working with Casey, we had only had poor to mediocre experiences outsourcing work to agencies... instead of needing babysitting like the other agencies we worked with, he was not only completely dependable but also gave us sound suggestions on how to get better results.”
“Since going with Casey and his team, we have had nothing but wins! They are great communicators, but more importantly, have got awesome results with low lead costs.”
“As an experienced health professional I am a hard sceptic. Casey and his team over delivered on my project with an A+ website design having actively listened to every point I was seeking.”
“Casey has been an absolute standout! His personalised approach has been nothing short of incredible. We have had amazing results from the get-go.”
“Excellent company to deal with and their web design is incredible. Would use them again and again.”
“Casey was so empathetic and patient in listening to my ideas. He asked all the right questions and got me thinking on aspects I hadn't considered. He goes above and beyond.”
“If you're looking for a highly experienced, knowledgeable and ideas-driven marketing agency, look no further... He's helped transform our business from a fairly humble start-up to a fast growing and highly regarded service provider.”
“We have worked with Casey on a number of website projects and are super impressed with his promptness, communication, professionalism, and knowledge of the full suite of digital marketing... You and your team are second to none!”
“[They have] truly exceeded my expectations... They handle every detail with care, addressing any concerns or inquiries I had with remarkable responsiveness and genuine accommodation. The end result was nothing short of fantastic.”
Research & Articles
An NDIS provider website serves participants, families, support coordinators and plan managers. How to build one each of them can use, built to WCAG 2.2 AA.
WCAG 2.2 AA explained for small business: what the standard asks, the 6 new criteria since 2.1, what Australian law expects, and checks you can run yourself.
Conversion tracking breaks when people decline cookies or block scripts. How consent mode and server-side events keep your lead numbers useful and private.
Questions
What you need to know before we start a conversation.
Not answered here? Ask us directly
No, because there's no official WCAG certificate to give. A website accessibility audit reports how your site measures against WCAG 2.2 AA on the day we test it. It doesn't certify or guarantee compliance, and nobody selling a certificate can either. You get a dated record to build an accessibility statement on.
We test against WCAG 2.2 at level AA, the current W3C Recommendation. It carries the 2.1 criteria forward and adds newer ones on focus visibility, target size, dragging and accessible sign-in. Every finding in the report names the exact success criterion it fails.
We test with a desktop screen reader and a mobile one, on the browsers your visitors use. Each finding notes the combination we reproduced it on. That way your developer can check the fix in the same setup before marking it done.
It depends on how many templates and key paths are in scope, since that's where the testing hours go. A small brochure site moves faster than a booking platform. You get the dates in writing before you commit, along with a fixed quote.
Every audit gets a fixed quote with line items after a free 15-minute call. The price follows the templates and key paths we test, not the page count. If the testing takes longer than we planned, that's our problem, not another invoice.
Some of them overlap. Descriptive headings, link text and image alternatives help search engines read a page as well as people. We never sell an audit as an SEO fix. But the two rarely pull in different directions, and the fixes often help both.
It changes the weighting. Your booking and intake forms are usually the paths that matter most, so we test those first and hardest. That includes their error messages, which are often where a patient using a screen reader gives up and calls instead.
