Tools and methods for auditing website accessibility

Checking a website’s accessibility is a key step in ensuring WCAG compliance. There are many tools that allow audits to be carried out both automatically and manually.

Tools for automatically checking accessibility

  1. W3C Validator (validator.w3.org)
    This is a tool for automatically checking the validity of HTML and XHTML code. It analyses a website for compliance with current W3C standards, which affects accessibility and functionality. It can detect errors in the HTML structure that may cause problems with navigation and the operation of assistive tools such as screen readers. The Validator is helpful in ensuring a website’s basic WCAG compliance, although it does not ensure full accessibility on its own.
  2. WAVE (Web Accessibility Evaluation Tool)
    This is one of the most popular accessibility analysis tools. WAVE scans a website and identifies errors such as missing alternative text, poor contrast or problems with headings. It is a simple tool that can be run in a browser to obtain an immediate report.
  3. Google Lighthouse
    Lighthouse is a tool built into the Chrome browser that analyses a website’s performance, SEO and accessibility. It is very useful for an overall assessment of a website, including WCAG compliance.
  4. Axe Accessibility Tool
    A Chrome browser extension that scans a website for accessibility issues. The tool identifies technical errors such as missing ARIA labels or problems with keyboard navigation. It is often used by developers to detect problems early.
  5. HeadingsMap
    is a useful browser extension that allows you to analyse the HTML heading structure on a page. It lets you quickly check the heading hierarchy, which is crucial for accessibility and navigation, especially for screen reader users. It is always worth having it to hand when testing WCAG-compliant websites.

Manual auditing methods

Although automated tools are very helpful, they will not detect every problem. That is why manual accessibility testing is also important.

  1. Testing keyboard navigation
    Checking whether the entire website can be operated using a keyboard is crucial. It is worth making sure that all interactive elements, such as forms or menus, are accessible without using a mouse.
  2. Using screen readers
    Programs such as NVDA or JAWS allow you to simulate how blind people use a website. It is worth testing the website to make sure that screen readers read all elements correctly.
  3. Checking the website structure (UI/UX) and the arrangement of elements
    Manual accessibility testing should also include checking the overall structure of the website, meaning how interface elements are arranged and how consistent the messages to users are. It is crucial to make sure that:
    • Elements are arranged intuitively – It is important that users, including those using assistive tools, can easily find the information they need. For example, buttons, forms and navigation menus should be placed where users expect them to be.
    • Consistency of messages and labels – Every interface element should have clearly defined functions and consistent messages. For example, button and form labels must be unambiguous so that people using a screen reader can interpret them correctly.
    • Navigation and access to features – The website’s structure should be logical and consistent, with an appropriate heading hierarchy and easy movement between individual pages and sections.
      Checking UI/UX in the context of accessibility is crucial because a poorly designed website may be unusable for people with impairments or those using assistive tools.

Manual website testing is the most difficult and most painstaking stage of testing a website. It requires a thorough knowledge of WCAG principles, familiarity with UX/UI issues and the ability to use assistive tools to put yourself in the position of, for example, a blind person. It also requires working through many test scenarios. These range from freely navigating the website to checking the search function and how results are presented, checking forms, and checking that links that will take users away from the website communicate this appropriately.

Regular accessibility audits

Maintaining a website’s accessibility involves more than coding it once: it also requires ongoing work by editors, who must create content in accordance with the guidelines. Even after a website has been adapted to WCAG, it should be checked regularly to see whether updates or new features have introduced any new problems. This will ensure that the website remains compliant with regulations and that users have uninterrupted access to content. We have detailed guidelines for editors, available exclusively to our clients, that help maintain high accessibility standards.

If a website has already been properly programmed, maintaining its WCAG compliance is relatively simple. Remember not to make the most common mistakes 🙂

FSV Sp. z o.o. offers comprehensive support with accessibility audits and website optimisation, allowing your institution to meet legal requirements and adapt its website to users’ needs. In addition, if you need technical care and regular updates, we recommend our Dobry Webmaster service. As part of this service, we will create a backup, update the website and test whether everything works correctly after the updates.