What Is Included in a Web Accessibility Audit

When a business starts thinking about web accessibility, it is not always clear what it means and where to begin.

A web accessibility audit can help answer these questions, build understanding, and serve as a foundation for planning next steps.

But what exactly is checked during a web accessibility audit?

An audit is not a single check, but a comprehensive evaluation of a website across different aspects of accessibility.

A comprehensive accessibility audit typically includes checking:

• compliance with WCAG guidelines
• HTML page semantics
• keyboard navigation
• using the website with a screen reader
• usability of forms and other complex components
• visual accessibility of content

Such an audit is performed both manually and with automated tools.

As a result, the client receives a report with recommendations on what exactly should be fixed and how. This report becomes a starting point for planning tasks for the product team.

WCAG Evaluation

WCAG (Web Content Accessibility Guidelines) are globally recognized recommendations for ensuring content accessibility for all people. They are developed by the W3C (World Wide Web Consortium).

WCAG criteria are widely accepted guidelines for ensuring web accessibility.

These criteria cover the following aspects:

1. Perceivable. Information on the page must be available for perception. For example, visible, sufficiently contrasted, and images or videos must have text alternatives.
2. Operable. The website must be accessible for navigation using different methods, including keyboard-only navigation without a mouse.
3. Understandable. Information must be understandable, the interface should have a clear structure, and behavior should be predictable.
4. Robust. Content must be robust enough to be interpreted by assistive technologies such as screen readers.

Each of these aspects includes a number of recommendations.

In addition, there are three levels of conformance: A, AA, AAA.

Level A includes basic requirements, while level AAA provides the highest level of accessibility. Level AA is generally accepted and recommended.

A web accessibility audit includes checking WCAG criteria according to the selected level.

HTML Structure and Semantics Analysis

The structure of a page is extremely important for understanding information. It helps users quickly navigate and find the necessary content. This applies both to users of assistive technologies and to users with a mouse and keyboard.

HTML semantics ensures the correct use of tags on a page. For example, appropriate HTML elements should be used for headers, footers, headings, lists, links, and buttons.

This affects usability, visual appearance, and even SEO (Search Engine Optimization).

Checking semantics and page structure is part of a web accessibility audit.

During a web accessibility audit, the following is checked:

• whether the page structure is correct and clear
• whether semantic tags are used for different elements
• whether the heading hierarchy is correct
• whether the page includes landmarks that significantly improve screen reader navigation

Keyboard Accessibility Testing

Keyboard accessibility is important for everyone:

• for users with motor impairments
• for people with visual impairments and users of assistive technologies
• for users who do not have a mouse (forgot it, it ran out of battery, or it is broken)
• for people with temporary disabilities (for example, a broken arm)
• for those whose hands are occupied (for example, parents holding a child)

Therefore, keyboard navigation is one of the key requirements of web accessibility and is included in the web accessibility audit.

During accessibility testing, the following aspects are checked:

• whether the entire user journey can be completed without a mouse
• whether all interactive elements are accessible via keyboard
• whether the focus is visible and the user understands their current position
• whether there are any so-called “focus traps” (when focus gets stuck inside an element)
• whether the navigation order is logical and matches the visual structure

This stage requires manual analysis and cannot be fully covered by automated tools.

Screen Reader Testing

People with visual impairments use assistive technologies to access web resources. One of the most well-known examples is a screen reader — software that reads the website aloud.

Often, users with visual impairments perceive a website through audio. Therefore, it is especially important to provide complete and clear information about the page.

A web accessibility audit typically includes testing pages using a screen reader.

In particular, the following is checked:

• whether the spoken content matches what is displayed visually
• whether buttons, links, and other elements have accessible names
• whether the names of buttons and links are clear
• the page structure as announced by assistive technology
• the ability to navigate via landmarks and headings

Automated tools also cannot fully handle testing this aspect.

Visual Accessibility Testing

This stage of accessibility testing includes checking:

• the size of interactive elements
• color contrast between background and content
• the ability to zoom the page or increase text size
• visibility of focus during keyboard navigation

For example, WCAG defines recommended target sizes for interactive elements (buttons, icons, links). This makes interaction easier and is useful for mobile users and people with motor or visual impairments.

Meeting color contrast requirements is critically important, as many websites are difficult or impossible to read due to low contrast between text and background.

Some websites may also restrict page zooming, making them inaccessible for users with visual impairments or small screens.

Therefore, visual accessibility testing is an important part of a web accessibility audit.

Testing Complex Components

Complex elements may include:

• forms
• modals
• dropdowns
• menus
• carousels

Testing them is part of a web accessibility audit.

Such elements are often implemented without semantic tags and instead built as custom components to improve design and functionality. They are also rarely tested for accessibility.

These elements may be inaccessible via keyboard or incorrectly announced by assistive technologies.

For example, a menu may only work with mouse clicks and not be accessible via keyboard. A modal window may lack a way to close it.

Form accessibility requires special attention, as there are many requirements. For example, each field should have a visible label, instructions should be provided for fields with specific validation, and error messages should be clear and informative.

Use of Automated Tools

A web accessibility audit is conducted not only manually but also using automated tools (such as Google Lighthouse).

These tools help identify basic issues and areas for improvement, but they cannot fully replace manual testing. A comprehensive audit requires in-depth analysis of the user journey.

On our website, you can learn more about the difference between automated and manual accessibility testing.

What the Client Receives

During the audit, a report is prepared. This report includes a list of checked WCAG criteria, descriptions of issues with explanations and severity levels, and recommendations for fixing them.

This report becomes the basis for creating a roadmap to improve your product’s accessibility. Improvements do not have to be implemented all at once — they can be introduced gradually as separate tasks. A structured report makes this process much easier.

A web accessibility audit is a comprehensive website evaluation. It covers technical aspects, UX and user comfort, helps understand the current state of accessibility, and define priorities for improvement.