Accessibility testing: Automated WCAG checks for web applications

WCAG Compliance: Is your website accessible?

1. Submit your URL
2. Our experts analyze your website using QF-Test according to WCAG criteria: alt text, color contrast, keyboard navigation, ARIA roles, and more.
3. Receive an accessibility report with concrete recommendations within 2-5 business days -- no installation, no code, no obligation

Get your free accessibility check

How to test web applications for accessibility with QF-Test?

QF-Test comes with a dedicated test step for accessibility: the “Accessibility Checks” node. You add it to your test suite like any other step and specify which checks should run. A context-sensitive selection menu suggests suitable rules and parameters and inserts the correct syntax automatically.

You combine two approaches:

1. Checks with axe-core: The integrated open-source library checks your pages against WCAG 2.0, 2.1, and 2.2 (levels A and AA).
2. QF-Test’s own checks: QF-Test additionally checks the color contrast of icons and other graphical elements, the visibility of the keyboard focus, and the language attribute of the page.

Because QF-Test simulates real user interactions, you can test not only static pages but every state of your application, for example after login or in an open dialog.

Videos: Automated accessibility testing of web applications with QF-Test

Web Accessibility Testing with QF-Test

In this webinar, we will give a brief introduction to web accessibility and present the new accessibility testing features of QF-Test.

Automatically test the accessibility of your web application with QF-Test 9

In this video we show you how you can use QF-Test 9 to test the accessibility of your website or web application. It’s quick and almost completely automatic! We will also demonstrate some of the other abilities QF-Test has gained with version 9.

What sets QF-Test apart in accessibility testing

QF-Test combines established accessibility checks with functional UI test automation. That’s what sets it apart from pure scanners.

• Check dynamic states, too
  Static scanners usually only see the page that loads when it is first opened. QF-Test clicks through your application the way real users do. This lets you specifically check areas behind a login, open dialogs and menus, filled-in forms with error messages, and dynamically loaded content.

• Proven rules, no programming required
  axe-core is widely regarded as one of the standards for automated accessibility testing. Among other things, the library checks for missing alternative text, insufficient color contrast, and faulty ARIA roles and attributes according to WCAG 2.0, 2.1, and 2.2, levels A and AA. You define which rules run and how strict the checks are in the “Accessibility Checks” node.

• Additional checks beyond axe-core
  QF-Test adds its own checks to axe-core: it checks the color contrast of icons and other graphical elements, uses simulated keyboard navigation to verify that the focus is always visible, and makes sure that the page declares the correct language for screen readers. You can deliberately hide known low-priority issues from the report. For special requirements, you can create your own accessibility tests.

• One tool for functionality and accessibility
  You simply build accessibility checks into your existing test cases. There’s no need for a separate test suite, and functional errors and accessibility barriers show up in the same test run.

• Continuous testing in the CI/CD pipeline
  If the checks run with every build, you detect new barriers immediately. This keeps regressions from ever reaching production.

• Reports your team can work with
  QF-Test categorizes errors and warnings, highlights affected elements in the screenshot, and provides hints on how to fix them. Your team can see at a glance what to tackle first.

Interactive sample report

With QF-Test, testers receive precise evaluations with hints on how to resolve the problems found. Our test reports in HTML format are flexible and interactive.

Scroll down in the sample report, enlarge screenshots and messages with one click, and use the arrow keys to navigate quickly between entries.

What automation can and can’t do

Automated tests find technical errors quickly, reliably, and reproducibly. However, they don’t cover all WCAG criteria. Whether content is understandable or whether operation with a screen reader really works is ultimately up to people to judge. QF-Test takes the recurring checks off your team’s hands, leaving more time for the manual tests that matter.

Try out accessibility testing with QF-Test

Why is web accessibility important?

In an increasingly digital world, web accessibility ensures that digital content is accessible to everyone. In addition to fulfilling their social responsibility, companies benefit from a better user experience and a broader target audience.

Accessibility is also becoming increasingly relevant for compliance with legal regulations such as the EU Directive (EU) 2019/882, known as the European Accessibility Act (EAA), and its German implementation, the Barrierefreiheitsstärkungsgesetz (BFSG), which have applied since June 28, 2025.

A central element of digital accessibility is support for assistive technologies such as screen readers, Braille displays, or voice control. These technologies enable people with disabilities to use web applications effectively. It is therefore essential that websites are compatible with these assistive technologies.

Accessibility in development: from design to testing

Accessibility is an essential part of modern software development and web applications. Software testers and developers are faced with the task of testing websites for accessibility. Manual tests are time-consuming, and much of the work is repetitive. Automated accessibility tests or A11y tests (a numeronym for “accessibility”) can save a massive amount of time by efficiently identifying common problems, even during the software development phase.

Ensuring accessibility begins as early as the design process. By considering accessibility aspects early on, developers and designers can ensure that digital products are designed inclusively right from the start. This includes the selection of suitable color schemes, the clear structuring of content, and the intuitive placement of buttons.

A central component of accessible web development is the clean and semantically correct structuring of the source code. This enables assistive technologies such as screen readers to correctly interpret and render the content of a website. Among other things, this includes the correct use of HTML elements and ARIA roles. QF-Test supports developers in checking the source code for accessibility issues by performing automated tests in accordance with the Web Content Accessibility Guidelines (WCAG) 2.0, 2.1, and 2.2.

Which guidelines apply to accessibility testing?

Whether you’re a public body or a company: almost all legal requirements for digital accessibility refer to the same technical basis, the Web Content Accessibility Guidelines (WCAG) at level AA.

What does this mean for your tests? With QF-Test, you run automated checks against WCAG 2.0, 2.1, and 2.2, so you’re already prepared for the new version 4.1.1 of EN 301 549, which raises the requirements to WCAG 2.2. However, automated tests don’t cover all criteria. A complete conformance assessment also requires manual checks.

Procedures for testing accessibility in software

No single procedure can fully test accessibility. Manual and automated tests have different strengths and complement each other.

Manual accessibility testing

In manual tests, experienced testers check the software from the perspective of people with disabilities. Using screen readers, magnification software, or keyboard-only operation, they assess whether the application is not only technically but also practically usable. This is the only way to answer questions such as: Is the order of the content logical? Are instructions understandable? Does a complex dialog really work with a screen reader?

Automated accessibility testing

Automated tests take over the recurring technical checks. They deliver comparable results with every run and can be integrated into the CI/CD pipeline. This way, you notice immediately when a change introduces new barriers, long before they would show up in a manual audit.

The best of both worlds

The combination is the most efficient approach: automated tests continuously safeguard the technical basis and relieve your team of routine checks. The time saved goes into targeted manual tests where human judgment is needed. Especially in agile projects with short release cycles, this keeps accessibility at a good level over the long term.

Free accessibility check: Is your website accessible?

Accessibility requirements are here to stay — and many websites still aren't compliant. To give you a clear picture, we now offer a free, no-obligation accessibility check: share your URL, our experts analyze with QF-Test your site against WCAG standards, and you'll receive an interactive report with concrete recommendations within 2–5 business days.

No risk, no hidden costs — just clarity on what needs to be done.

Get your free accessibility check

Further information

• Accessibility testing for web applications: The online magazine “Informatik Aktuell” has published an interesting article on accessibility (in German) with several approaches and considerations.
• Accessibility testing: QF-Test compared to other tools – Tobias Kirsch, Senior Software Engineer at Adesso, evaluates the QF-Test beta developer version with a11y checks in a blog post by Adesso (in German).
• QF-Test special webinar: Automated accessibility testing with QF-Test
• Bachelor’s thesis “Automated Testing of Accessibility” with QF-Test by Daniel Rieth, 2025 (German PDF)

FAQs about web accessibility

Can accessibility tests be integrated into CI/CD pipelines?

Yes. The checks run as part of your existing test runs, so you notice immediately when a change introduces new barriers.

Yes. The checks run as part of your existing test runs, so you notice immediately when a change introduces new barriers.

Accessibility Testing

Do I need programming skills for accessibility testing with QF-Test?

No. QF-Test is a low-code tool, and the procedures for accessibility testing are ready to use.

No. QF-Test is a low-code tool, and the procedures for accessibility testing are ready to use. If you like, you can still build your own tests with simulated user interactions.

Accessibility Testing

How can I find out if my website is accessible?

With the free accessibility check: submit your URL and receive the report within 2–5 business days.

With the free accessibility check: submit your URL and within 2–5 business days you’ll receive a report with concrete recommendations for your website. Our experts use QF-Test to analyze your website against WCAG criteria such as alternative text, color contrast, keyboard navigation, and ARIA roles.

Request your free check now

Can accessibility be tested fully automatically?

No. Automated tests find technical errors quickly and reproducibly. Comprehensibility and logical structure still require manual review.

No. Automated tests find technical errors such as missing alt texts, incorrect ARIA roles, or low contrast quickly and reproducibly. Comprehensibility and logical structure still require manual review. That said, meeting the technical criteria already goes a long way toward helping users.

Accessibility Testing

What does QF-Test check in accessibility tests?

QF-Test integrates the axe-core library without any programming effort. In addition, it provides its own checks, such as a color contrast check for graphical elements.

QF-Test integrates the axe-core library without any programming effort. In addition, it provides its own checks, such as a color contrast check for graphical elements. More custom checks, for example for focus visibility, have been announced.

Accessibility Testing

What is the difference between WCAG, BITV, BFSG, and EAA?

WCAG is the technical standard. EN 301 549 and BITV 2.0 translate it into European and German requirements. The EAA and BFSG define who is required to provide accessibility.

The WCAG (Web Content Accessibility Guidelines) are the technical standard for accessible web content. EN 301 549 and the German BITV 2.0 translate it into European and German requirements, respectively.

The EAA (European Accessibility Act) and its German implementation, the BFSG (Barrierefreiheitsstärkungsgesetz), define who is required to provide accessibility – since June 2025, this includes many companies.

Accessibility Testing

Which WCAG level does my website need to meet?

Usually level AA. This is the level referenced by EN 301 549 and the legal requirements.

Usually level AA. This is the level referenced by the European standard EN 301 549 and by legal requirements such as Germany’s BITV 2.0 and BFSG.

The requirements that apply in a specific case depend on factors such as industry, company size, and the type of digital service. Some areas may also be subject to different or additional rules. If in doubt, please seek legal advice on which requirements are binding for your service.

Note: This information is intended as general guidance and does not constitute legal advice.

Accessibility Testing

Benefits for QA engineers

How does QF-Test support testers in doing test automation? Intuitive usability & clear structure, efficient test creation, maintenance & debugging.

Benefits for software developers

API access, Java, Groovy, Jython & JavaScript, unit integration, modularization of extensive tests, abstraction of complex UI components.

Benefits for decision-makers

Fast ROI, faster in the market, low maintenance effort, established for 20 years, daily monitoring, better quality.