Accessibility

Website accessibility audits and remediation.

Find out what needs improving, fix the barriers affecting your users, and understand where your website stands. We assess and improve existing websites, including sites you manage on behalf of your clients.

Ways we can help

Three places to start.

Most people arrive at one of these. You do not need to know which before you talk to us.

01

Accessibility assessment

We review an agreed selection of pages, templates, components and user journeys, then set out what is getting in your users’ way and what to do about it, in the order worth doing it.

02

Remediation

We work from our own findings or from a report you already have, and implement the agreed fixes in your existing website or application.

03

Retesting and ongoing support

We check that the agreed changes did what they were meant to, document anything still outstanding, and stay available as the site develops.

Automated tools are the first pass, not the audit. axe-core finds a real class of problem quickly and clears a lot of noise, but a large share of the WCAG success criteria cannot be checked by a machine at all. Whether a link still makes sense read out of context, whether an error message tells you how to recover, whether a form can be completed without a mouse: those are judgements, and they need a person.

So we run the automated pass across the pages in scope, then work through the same pages by hand. Keyboard-only navigation, screen reader behaviour, and contrast measured against the colour actually behind the text rather than the one in the design file. It is how we test this site, and it is the same method we would point at yours.

Already have a report

Bring the audit you already have.

You do not need to buy another one before we can help.

Send us the findings

Plenty of organisations arrive holding a report and no clear route from it to a working website. Sometimes it came from a specialist auditor, sometimes from a procurement requirement, sometimes from a tool that produced several hundred rows of output and no order to do them in.

We will read what you have and investigate it against the live site. Which findings are real, which are one underlying problem counted many times, which are the tool misreading the page, and which need a decision from you rather than a change to the code. Then we scope the implementation and the retesting against it.

If the report turns out to have gaps, we will tell you where they are and what it would take to close them. That is a smaller piece of work than starting again.

For agencies and IT providers

The website is not yours, and the deadline still is.

Agencies, IT providers and internal teams often carry responsibility for a website somebody else owns. You may have inherited it, you may support it, or you may simply be the person the question landed on.

We can work with your existing team rather than around them. We agree who does what, what access we need and what we will not touch, and we write the findings so they can be put in front of your client rather than translated first.

White-label is normal here. We already work under other agencies’ brands on builds and technical work, and this is no different: you keep the relationship and the client hears it from you.

Standards

What WCAG 2.2 actually asks for.

WCAG 2.2 is the current W3C Recommendation, published in December 2024. It sets out success criteria at three levels: A is the minimum, AA covers everything in A as well, and AAA covers everything in A and AA. Most UK obligations and procurement requirements are written around AA.

Version 2.2 added nine success criteria, covering things like keeping the focus indicator visible, not depending on a dragging movement, minimum target sizes and authentication that does not require remembering something. It did not replace the earlier versions: a page meeting 2.2 also meets 2.1 and 2.0.

We agree the level with you at the start and aim for the strongest practical outcome rather than the minimum, including individual AAA criteria wherever your content allows. What we will not do is promise AAA across a whole site. The W3C is explicit about that: “It is not recommended that Level AAA conformance be required as a general policy for entire sites because it is not possible to satisfy all Level AAA success criteria for some content.” Meeting selected AAA criteria and conforming at AAA are different claims, and we keep them separate.

One more thing worth saying plainly: a clean automated scan is not conformance. Zero violations means the machine-checkable part passed. It says nothing about the criteria that need a person to judge them, which is most of them.

How it works

What actually happens.

01

We talk, and we look

A conversation about the site and what has prompted this, then a look at the website or at the report you already hold. No charge for that part.

02

We agree the scope

Which templates, which components and which complete journeys. A journey matters more than a page count: a checkout that fails at step four is a failure whatever the other pages score.

03

Findings and a proposal

What we found in priority order, with what it would take to put each one right. You keep the findings whether or not you go on to have the work done.

04

Implementation

We make the agreed changes in a development or staging environment, so nothing reaches your live site untested.

05

Retesting and handover

We check the changes did what they were meant to, document what remains and why, and hand over something your team can keep up.

Some of it sits outside the website. Embedded booking systems, payment providers, PDFs and other documents, and video captions are the usual examples, and they are often owned by somebody else. We will tell you early which of those apply to you, what we can change directly, and what needs a conversation with the supplier.

Pricing

Scoped and priced before it starts.

The cost depends on the website, the issues involved and whether you already have an audit. We agree the scope and the price before work begins, with assessment, implementation and retesting identified separately so you can see what each part is costing you.

The first conversation is free and happens through the same discovery call as everything else we do. If we need to do chargeable investigation before we can scope the work properly, we will agree that with you before it starts.

Questions

The ones we get asked.

Can you fix issues identified by another accessibility auditor?

Yes, and it is a common way to start. Bring the report and we will work out which findings are real, which are the same underlying problem counted several times, and which are the tool misreading the page. Then we scope the fixes and the retesting against it. You do not need to buy another audit first.

Do we need a new website?

Usually not. We look at what you have before recommending anything, and most accessibility problems are fixable in the site you already own. A rebuild is the answer when the underlying markup or the platform makes the fixes cost more than starting again, and if we think that is your situation we will show you why rather than assert it.

Can you work with a website we manage for a client?

Yes. Agencies and IT providers are a large part of this work. We agree responsibilities and access up front, work alongside your existing team, and write the findings so you can put them in front of your client. We are happy to work white-label under your brand.

What is included in an accessibility assessment?

An agreed selection of pages, templates, components and complete user journeys. An automated pass with axe-core, then manual checking of the same material: keyboard-only navigation, screen reader behaviour, and contrast measured against the colour actually behind the text. You get prioritised findings with what it would take to fix each one.

Can you guarantee WCAG AAA?

No, and you should be wary of anyone who does. The W3C itself does not recommend AAA as a general policy for a whole site, because some content cannot satisfy every AAA criterion. We agree a target level with you, work to it, and meet individual AAA criteria wherever your content allows. Meeting selected AAA criteria and conforming at AAA are different claims and we keep them separate.

How long does remediation take?

It depends on how much there is and how the site is built, so we will not put a number on it before we have looked. What you will get is a real timeline once the scope is agreed, rather than an optimistic one at the enquiry stage.

Can you help with ongoing accessibility?

Yes. Accessibility is not a state you reach once, because content and features keep arriving. We can retest after releases, review new templates before they ship, and stay available to the team doing the work. That can run as part of a support arrangement or as occasional pieces.

What do you need from us to get started?

The website address, whether you already have an accessibility report, and any deadline you are working to. If the work goes ahead we will also need access to a development or staging environment, and a named person who can answer questions about content and third-party systems.

Get started

Tell us what needs improving.

Send the website address, whether you already have an accessibility report, and any deadline you are working to. That is enough for us to tell you what is involved.

Or email hello@oynk.co.uk