Agree what will be evaluated
We identify the website, page sample, templates, documents, embedded tools, and critical tasks. The proposal records the target standard and level, test approach, and exclusions so you know what the assessment covers.
Website accessibility assessment & remediation
Make your website easier for everyone to use.
Find the barriers in the journeys people rely on. Repair the agreed issues. Check that the changes help someone complete the task.
GATE Express Carwash
Client project
GATE Express Carwash
A website and location experience for a car-wash network, with search structure and accessibility-focused work.
Explore the project ↗A website accessibility audit needs a defined scope, a stated target, and human review. We combine automated checks with manual testing of representative pages and journeys, then turn the findings into practical design, content, and development work.
Explore the experience
Turn a finding into a working improvement.
Follow an illustrative form issue from observation to retest. This is a demonstration of our approach, not a client audit result.
Find the barrier
A visitor cannot tell what needs correcting.
An assessment checks whether errors are identified, associated with the relevant fields, and understandable. A screenshot or automated score alone cannot tell the whole story of completing a form.
- Choose the journey
- Reproduce the issue
- Record the barrier
Make the repair
Give the visitor useful feedback.
The repair can include explicit field labels, a specific error message, an associated explanation, and appropriate focus behaviour. Fixing the shared component can help every page that uses it.
- Assign the owner
- Repair the component
- Review affected pages
Retest the journey
Check the task, not just the changed code.
Repeat the affected journey with the agreed keyboard and assistive-technology checks. Record what passed, what remains, and any third-party dependency that your team cannot directly change.
- Repeat the task
- Record the result
- Track remaining work
What we deliver
A clear scope. Useful findings. Accountable repairs.
We agree the deliverables, responsibilities, and acceptance checks with you before work begins.
Talk through your scope ↗Look beyond an automated score
Automated checks help identify certain issues. Manual review is needed for keyboard navigation, focus, form feedback, headings, content alternatives, and the way a complete journey works. The sample and methods are recorded with the findings.
Prioritise work people depend on
We group issues by impact, affected components, and responsibility. Your team can see which repairs unblock a critical task, which apply across templates, and which require a third-party vendor to act.
Keep accessibility in the publishing process
New content and third-party changes can introduce new barriers. We can include editing guidance, reusable accessible patterns, and an agreed review process in the handover. Ongoing checks are scoped around how your website changes.
From the first conversation to handover
You will know what happens next.
- 01
Make the plan
We review your current setup, your priorities, and the people who need to use it. You get a defined first phase and clear dependencies.
- 02
Review the work
You see the agreed direction and working pages as they develop. Decisions and feedback are tied to the scope and the people responsible.
- 03
Check and hand over
We verify the agreed journeys, resolve release issues, and give your team the access and guidance needed to run the result.
Before you decide
Your questions, answered.
Does an accessibility audit certify legal compliance?
No. An assessment documents findings for the agreed sample, methods, and target at a point in time. It does not guarantee that every page or future change meets every legal obligation. Your legal adviser determines the obligations that apply to your organisation.
Can you repair another developer’s website?
Often, yes. We first confirm platform access, ownership, available source, and third-party constraints. Findings are assigned to the party able to change them, and the proposal distinguishes work we can deliver from dependencies.
Can accessibility be built into a new website?
Yes. We can include accessibility requirements in the content model, design patterns, development, and acceptance checks. It is easier to review components and journeys as they are built than to leave all repairs until launch.
What do we receive?
The agreed assessment record, reproducible findings, priorities, and repair recommendations. When remediation is included, we also document the changes and retest results. The deliverables and sample are stated before work starts.
Find the right next step.
Let’s make it useful
Tell us what you need to change.
Share your current website, the challenge, and any timing or platform constraints. We will help you define a practical starting point.
Discuss your accessibility scope ↗