How we test
By hand, the way people really use it
We use the same tools people with disability use every day. Here’s how it works, in plain words.
Real tools, real people
Our method
Four steps, every time
1
Pick a fair sample
We follow WCAG-EM, the W3C’s method, to choose screens and tasks that represent your whole service.
2
Scan first
It’s quick, but scanners only catch about 30% to 63% of issues.
3
Test by hand
Screen readers, keyboard only, zoom and colour checks, on desktop and mobile.
4
Rank by impact
The issues that stop people come first.
In plain words
WCAG 2.2 Level AA is the standard most Australian rules point to. It’s what we test against.
Our toolkit
The tools we test with
Five screen readers across the devices people actually use.
Windows laptop
NVDA with Firefox or Chrome
Windows laptop
JAWS with Chrome
Mac
VoiceOver with Safari
iPhone
VoiceOver with Safari
Android phone
TalkBack with Chrome
Also on every job: keyboard only, zoom to 200% and 400%, reflow on a narrow screen, colour contrast, and captions for any media.
Severity
How we rank issues
So you always know what to fix first.
Critical
Stops someone finishing a task.
High
Possible, but only with real difficulty.
Medium
Causes errors or extra effort.
Low
A small barrier, or a best-practice gap.
Within each level, busy screens and essential tasks come first.
In every report
What every issue includes
Where it happens
The WCAG rule it breaks
How serious it is, and who it affects
Steps to see it for yourself
A recommended fix, with code where it helps
A screenshot
Testing doesn’t replace people
Expert testing finds barriers. For important services, we also recommend paying people with disability to try them, and we can help you plan it.
See the method in action
The sample report shows exactly what you’ll get.