skip to content

accessibility 7 min read

WCAG audit: what it involves, what I check and how much it costs

What is a WCAG audit, what does it cover and how much does it cost? How it runs step by step and how an automated audit differs from a manual one.

WCAG audit, a laptop with an accessibility checklist

A WCAG audit answers one question: can your website be used comfortably, including when someone does not use a mouse or relies on a screen reader. Below I explain what I check, how an audit runs and how much it costs.

What a WCAG audit is

A WCAG audit is a check of a website or store for digital accessibility. It shows whether people with different needs can use your site comfortably.

WCAG describes the rules for building websites that are accessible to more users. That includes people who are blind, have low vision, use a keyboard or a screen reader, or have difficulty reading small elements.

A good WCAG audit checks real use of the site. I look at the structure, content, forms, contrast, keyboard operation, error messages, headings, buttons, links and interactive elements.

The result? You know where the site blocks the user, which errors are most urgent and how to fix them.

When you need an accessibility audit

You need an accessibility audit when you want to check whether your site meets the WCAG requirements and can be used without barriers. Most often an audit like this is done before a rebuild, after a new site goes live or before an important accessibility deadline.

A WCAG audit makes sense if you run an online store, a company website, a portal with bookings, an educational site, or the website of a medical practice, a counselling centre, a foundation or an institution.

It is also useful when you have contact forms, a shopping basket, payments, appointment booking, PDF files, video content or user panels. The more places where a user has to click, type or understand something, the greater the risk of errors.

A common signal? Someone reports that something “can’t be done” on the site. They cannot send a form. They cannot see a button. They do not know where the error is. An audit helps to find the cause.

What a WCAG audit covers (scope)

Checking the elements of a page during a WCAG audit

AI-generated image

A WCAG audit covers checking the site against the accessibility principles and practical user scenarios. The scope depends on the size of the site, the number of subpages and the types of features.

Most often I check a representative sample of the site. For example the home page, a service page, a blog post, the contact page, a form, the basket, the checkout, the user account and selected templates.

In an audit I analyse, among other things, the heading structure, link descriptions, alternative text for images, colour contrast, text size and readability, focus order, keyboard operation, forms, error messages and the accessibility of dynamic elements.

For a store there are also product pages, variants, filters, the basket, delivery, payment and confirmations. For a service website more of the emphasis goes on forms, content, navigation and contact sections.

I also check whether the content is understandable. Accessibility is language as well. If an error message reads like a technical riddle, the user is left alone with the problem.

How an audit runs, step by step

How a WCAG audit runs, site analysis and notes

AI-generated image

A WCAG audit runs in stages: I agree the scope with you, check the site, describe the errors and prepare recommendations. That way you know what is happening at every step.

First we choose the subpages and features to check. For a small site the scope tends to be simple. For a store or a larger site, you have to choose the paths that matter most to the business.

Then I do the technical and usability analysis. I use automated tools, test keyboard operation, and check the code structure, forms, contrast and the behaviour of interactive elements.

Next I sort the errors by importance. A minor problem with an icon’s description is treated differently from a form that cannot be sent without a mouse.

At the end you get a report. No padding. What the problem is, where it occurs, how it affects the user and how it can be fixed.

Automated and manual audits: how they differ

An automated audit finds some of the errors quickly, and a manual one shows how the site works in practice. Combining both methods gives the best result.

Automated tools, for example WAVE, are useful. They can detect missing descriptions, some contrast problems, errors in the HTML structure and basic violations of the WCAG rules.

They have limits, though. A tool can check whether an image has an alternative description, but on its own it cannot judge well whether that description really helps the user. It can also miss a problem in a form that only appears after a specific click.

A manual audit lets you go through the site like a real user. I check whether you can move around with a keyboard, whether the focus is visible, whether the order of the elements makes sense and whether the messages lead the user onwards.

If you want a reliable answer, an automated scan alone is not enough. It gives a good start, but decisions about fixes should be based on manual verification.

What you get after the audit (report and recommendations)

After the audit you get a report with a list of problems, their location, their weight and recommendations for fixing them. The document is meant to help you decide what to fix first and how to plan the work.

The report should be understandable to the site owner, the project manager, the designer and the developer. That is why I describe errors in plain language and add technical details where they are needed for implementation.

In practice the report contains a description of the problem, an example from a specific subpage, the impact on the user, a reference to the WCAG area and a recommended fix. For larger sites prioritisation works well too: urgent, important, to fix in the next iteration.

I often prepare a short summary for the decision maker as well. That way you do not have to dig through the whole document to know what state the site is in and how much work may be ahead of you.

How much a WCAG audit costs (indicative range)

The cost of a WCAG audit depends on the size of the site, the number of templates, the features and how detailed the report needs to be. A simple company website will cost less than a store with a basket, payments and a customer account.

As a guide, a small audit of a few subpages can cost from a few hundred to a few thousand PLN. A larger audit of a store, portal or system with many user paths usually needs an individual quote.

The price is driven mainly by the scope. What counts is the number of unique views, forms, language versions, files to check, interactive components and scenarios that have to be gone through by hand.

The form of the report matters too. A short list of errors costs less than a full document with a description of the impact, priorities, recommendations for the developer and a walkthrough of the results.

If you want to compare quotes, check whether the audit includes manual tests. An automated analysis alone may look attractive on price, but it often leaves the most important question unanswered: can a user actually get through the site?

FAQ

How long does a WCAG audit take?

A small audit can take a few working days. For a larger site or store the time depends on the scope, the number of views and the features to check.

Is a WCAG audit enough to make a site accessible?

An audit shows the problems and gives recommendations. Accessibility itself only appears once the fixes are in place and the most important elements have been checked again.

Does the whole site have to be checked?

For large sites a representative sample is often checked. The most important templates and paths are chosen, the ones that best show the state of the whole site.

Can an automated tool replace a manual audit?

It can help, but it will not replace a manual check. Automated tools detect some of the errors, and many problems only come out when real use of the site is tested.

Does a WCAG audit apply to an online store too?

Yes. In a store the product page, variants, filters, basket, forms, delivery, payment and post-purchase messages matter most.

What comes after the audit if the report shows a lot of errors?

It is best to start with the problems that block the user in the most important actions. After that you can move on to changes that improve comfort, readability and the consistency of the whole site.

Filip Chrapek

Let's work together

What do you need?
Budget
When?

Prefer email? hi@philgood.dev