Questions 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.

Permalink

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.

Permalink

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.

Permalink

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.

Permalink

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.

Permalink

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.

Permalink

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.

Permalink

QF-Test Questions & Answers

We use "Matomo" cookies to anonymously evaluate your visit to our website. For this we need your consent, which is valid for twelve months.

Cookie Configuration

Functional cookies

We use functional cookies to ensure the basic functionality of the website.

Performance and statistics cookies

We use Matomo for analyzing and optimizing our website. Cookies permit an anonymous collection of information that help us offering you a clear and user-friendly visit of our web pages.

Cookie details
Description Vendor Lifetime Type Purpose
_pk_id Matomo 13 Months HTTP Contains a unique, pseudonymized visitor ID internal to Matomo for recognizing returning visitors.
_pk_ref Matomo 6 Months HTTP Used to track from which website the anonymized user proceeded to our website.
_pk_ses Matomo 1 Day HTTP The Matomo session cookie is used to track the visitor's page requests during the session.
_pk_testcookie Matomo Session HTTP Used to check whether the visitor's browser supports cookies.
_pk_cvar Matomo 30 Minutes HTTP Temporarily store data about the visit.
_pk_hsr Matomo 30 Minutes HTTP Temporarily store data about the visit.