Web accessibility, Melbourne
Websites everyone
can use.
Accessibility checks, fixes and new builds to WCAG 2.2 AA. We test by keyboard, screen reader and zoom, as well as with a scanner, so your site works for every customer.
- HTML5
- CSS
- JavaScript
- WordPress
- Shopify
- Lighthouse
Why it matters
One in five Australians
has a disability.
People with disability are not a small group. They are a large share of your customers, and that share grows every year as people get older.
- 21.4% of Australians have disability
- 5.5m Australians with disability
- 50%+ of Australians aged 65 and over have disability
The audit
What an audit
checks.
Example screens from an accessibility audit. They show the checks behind a site that works for everyone.
What's included
Everything WCAG 2.2 AA
asks for.
To meet level AA, a site must pass 55 rules, called success criteria. We test against all of them and fix what fails in the code.
-
Audits to WCAG 2.2 AA
Every template and main task checked against all 31 level A and 24 level AA rules. We use automatic scans and test by hand.
-
Keyboard and screen reader
Every control works with a keyboard, and the focus is always visible. We also test with the NVDA and VoiceOver screen readers.
-
Colour and contrast
Text at 4.5:1 or better and interface parts at 3:1. Colour is never the only way to show meaning.
-
Forms that help
Visible labels, clear error messages, autofill, and never asking for the same thing twice (new in WCAG 2.2).
-
Motion and media
Animation that respects the reduced motion setting and can be paused. Captions on video, and nothing that flashes.
-
Touch targets
Tap areas of at least 24 by 24 pixels, and a simple option for anything you would normally drag (both new in WCAG 2.2).
-
Structure and semantics
Real headings, landmarks, lists, and link text that makes sense on its own. Search engines and AI tools use this structure too.
-
We fix what we find
We fix what we find in your WordPress or Shopify theme, or work with your developers. Then we test again.
-
Accessibility statement
A plain statement of what the site meets, what we are still fixing, and how people can contact you.
How we work
Audit, fix,
then prove it.
Automatic tools find only some accessibility problems. Most of the work is testing by hand, the way people really use the site.
-
Scan
Automatic checks on every template find the easy problems: contrast, missing labels and empty links.
- axe-core
- Lighthouse
-
Test by hand
Keyboard only, screen readers, 200% zoom and a 320-pixel screen, through your main tasks.
- NVDA
- VoiceOver
- Zoom
-
Fix
Fixes go into the theme and its parts, so each fix works across the whole site at once.
- WordPress
- Shopify
-
Retest and record
We test everything again. You get a report to keep and an accessibility statement ready to publish.
- Report
- Statement
-
Keep it accessible
We check new pages and releases, so a redesign or a new plugin does not undo the work.
- Monitoring
The law
The law already
expects it.
In Australia, the Disability Discrimination Act 1992 makes it illegal to treat people with disability unfairly when you offer goods and services. That includes websites and apps. In 2025 the Australian Human Rights Commission published guidelines on equal access to digital goods and services. They point to the latest version of WCAG as the standard to meet. We are not lawyers, but we build to that standard and we document it.
- WCAG 2.2 AA as the target
- Proof of testing that you can keep
- An accessibility statement to publish
- Testing again after big changes
In the details
The fixes people
notice most.
The changes people notice first when a site becomes accessible.
-
Forms Labels that stay visible, and errors that say how to fix them. -
Display options High contrast, bigger text and no motion, added on top of an accessible build. -
Touch targets Every tap area checked against the WCAG 2.2 minimum size.
Good for everyone, and for search
Most accessibility work helps many more people than it was made for. Captions help in a noisy office. Strong contrast helps in bright sun. Big tap areas help on a small phone. Clear forms help anyone in a hurry.
It also helps machines. Screen readers need alt text, real headings, clear links and fast, stable pages. Search engines and AI tools use the same things to understand a page. That is why we treat accessibility and SEO & AI search as one job.
Why not an overlay?
An accessibility overlay adds a toolbar on top of the same code. It does not fix missing labels, broken keyboard access or a confusing structure. And it does not make a site meet WCAG. The fix belongs in the code and the content. Display options like the ones on this site are an extra on top of an accessible build. They never replace one.
Questions
What people ask
about accessibility.
The Web Content Accessibility Guidelines (WCAG) are the world standard for web accessibility, published by the W3C. Version 2.2 came out in October 2023 and added nine new rules. Level AA is the level most laws and policies ask for. It has 55 rules in total.
The Disability Discrimination Act 1992 covers goods and services, and that includes websites. People can make a complaint to the Australian Human Rights Commission. We can’t give legal advice, but WCAG 2.2 AA is the accepted standard to build to.
No. An overlay sits on top of the same code, so the real problems stay. Real fixes are made in the theme, its parts and the content.
Most sites are made from a small number of templates. So we check every template and the main tasks, like contact, booking or checkout, instead of every single page.
Yes. Most fixes go in the theme, so they work across the whole site at once. We fix, test again and document the work. We can also train your team to keep new content accessible.
Get in touch
Is your site working
for everyone?
Send us your website address. We will do a first check and tell you what we find.