Accessibility evaluationFind what’s locking
Find what’s locking
people out.
I check agreed pages and tasks for the barriers that stop disabled people using your service, and show your team exactly how to reproduce and fix each one.
At a glance
- Good for
- You need to know which barriers are real, how to reproduce them, and what to fix first.
- Who does it
- Brian, start to finish
- The fixes
- Built by whoever you choose
- Price
- Agreed in writing before we start
The real question
What stops people using this, and can we show it every time?
01 / Use this when
You need to know which barriers are real, how to reproduce them, and what to fix first.
02 / How I do it
Manual and automated checks on an agreed set of pages. Testing with specific assistive technologies is agreed up front.
Not a slide deckWhat lands
What lands
on your desk.
Every barrier with steps to reproduce it, and the relevant criterion where one applies
What to fix, and who on your team owns it
A retest, if it’s in the scope
How it runsFrom “we think”
From “we think”
to “we saw it”.
Agree what’s covered
Pages, checks, access and what’s out, all written down.
Record the barriers
Each one with steps anyone on your team can repeat.
Fix and check
Your team fixes. A retest, if scoped, checks the fixes worked.
Proof, not promisesSee it for
See it for
yourself.
See how a finding is written up, from what I saw to what to fix.
- Guidance documentsfailed accessibility checks
- Application form
- Help by phone
The guidance people needed failed accessibility checks.
It lived in documents that were hard to use on a phone, yet the form depended on them. Sessions included people using assistive technology and people applying for someone else.
Before we start
What to bring.
The service and what it’s built with, the pages that matter most, barriers you already know about, access details, and what the report is for.
Build your brief ↗