Manual WCAG Accessibility Audit – What It Is and How It Works in Practice

What Is a Manual Accessibility Audit?

A manual accessibility audit is a professional evaluation of a website, online store, or application for compliance with WCAG, the international standard for digital accessibility.

Its purpose is to verify whether the service can be comfortably used by people with disabilities — for example, people who are blind, have low vision, navigate using only a keyboard, or experience cognitive difficulties.

This is important because many accessibility issues are not visible at first glance. A website may look modern and function correctly from a technical perspective, yet still be very difficult for some users to navigate.

A manual audit helps identify such barriers, describe them clearly, and recommend how to fix them.

Why Is the Audit “Manual”?

The term means that the website is not evaluated solely by automated tools. Instead, it is reviewed by an accessibility specialist who navigates through it like a real user and analyzes all key elements.

For example, they check whether the entire menu can be accessed using only a keyboard, whether the contact form explains errors clearly, whether a “Buy Now” button is correctly announced by a screen reader, or whether content remains readable after zooming the page to 200%.

That is why a manual accessibility audit provides a much more complete picture than an automated scanner alone.

How Does a Manual WCAG Audit Work in Practice?

The process usually begins with understanding the website and defining the audit scope. A simple company website with a few pages requires a different approach than a large e-commerce store with a cart, payments, customer accounts, and hundreds of products.

Next, the auditor reviews the most important user journeys. This commonly includes:

• the homepage,
• navigation menus and search,
• forms,
• the login process,
• purchases or inquiry submissions,
• contact pages,
• the mobile version,
• dynamic elements such as pop-ups or dropdown menus.

For example, if a user wants to subscribe to a newsletter, the form should clearly indicate which fields are required and provide a specific message after an error, such as “Please enter a valid email address” instead of a generic message like “An error occurred.”

Are Automated Tools Used During the Audit?

Yes. A professional manual accessibility audit often uses automated tools, but only as support.

These tools can quickly detect missing form labels, insufficient text contrast, incorrect heading structure, or issues in ARIA code. This helps identify some technical problems more efficiently.

However, they do not replace human review. An automated tool cannot determine whether an error message is understandable, whether navigation is logical, or whether a checkout process can be completed by someone using only a keyboard.

That is why the best results come from combining automated testing with expert manual analysis.

Screen Reader Testing

One of the most important stages of an audit is testing with screen readers. These are programs used by blind users and some users with low vision that read website content aloud or output it to a braille display.

During the audit, the website is tested with popular solutions such as NVDA, JAWS, VoiceOver, and TalkBack.

Example issue: a button may look correct visually, but if it does not have a proper accessible name in the code, a screen reader may announce it only as “button,” without explaining its purpose. The user would not know whether it means “Search”, “Add to Cart”, or “Close.”

These issues are often invisible to people testing the site only visually.

Testing on Different Devices and Browsers

Accessibility should be tested in real-world conditions, which is why an audit should not be limited to one computer and one browser.

A website may work correctly in Chrome on a laptop, while in Safari on an iPhone the menu may be difficult to use or a form may lose keyboard focus. It is also common for elements that work well on desktop to become problematic on mobile devices.

For this reason, a professional audit includes testing across multiple devices, operating systems, and browsers.

Testing with People with Disabilities

A highly valuable addition to an audit is usability testing with people with disabilities. These are moderated research sessions in which a real user performs specific tasks on the website while a moderator observes the entire process.

For example, a blind participant may be asked to find a product and add it to the cart. The moderator observes where difficulties appear, asks follow-up questions, and collects feedback. This makes it possible to understand the real user experience, not just checklist compliance.

Such sessions often reveal issues that even experienced auditors may miss — for example, overly complex language, confusing page structure, or too many steps in a process.

Why Does One Audit Take a Few Days and Another Several Weeks?

This depends mainly on the size and complexity of the project.

A small company website with a few pages can usually be reviewed relatively quickly. However, if the audit covers an online store, e-learning platform, or a large system with multiple user roles, the number of scenarios increases significantly.

In such cases, the audit may need to cover not only the homepage, but also login, registration, search, cart, payments, user accounts, documents, mobile views, dynamic components, and screen reader compatibility.

Additional time is also required to prepare a detailed report with issue descriptions and implementation recommendations.

That is why a simple audit may take a few days, while a comprehensive one can take several weeks.

What Does a Company Receive After the Audit?

The result of the audit should be a practical report that helps the team implement improvements.

A good report does not end with saying “this is wrong.” It should explain:

• what the issue is,
• who it affects,
• which WCAG requirement it relates to,
• how to reproduce the issue,
• what the business risk is,
• how to fix it from both technical and design perspectives.

This makes the document useful for developers, UX designers, QA teams, and product owners.

Why Is a Manual Accessibility Audit Worth Doing?

A manual accessibility audit helps meet legal requirements while also improving the quality of a digital product.

Better accessibility means easier forms, clearer content, simpler navigation, and less frustration for users. Everyone benefits — not only people with disabilities.

For many companies, an audit is also a way to increase conversion rates, reduce abandoned checkout processes, and build a professional brand image.