Yes. The checks run as part of your existing test runs, so you notice immediately when a change introduces new barriers.
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.
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.
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.
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.
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.
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.
Can accessibility be tested fully automatically?
No. Automated tests find technical errors quickly and reproducibly. Comprehensibility and logical structure still require manual review.
Can accessibility be tested fully automatically?
No. Automated tests find technical errors quickly and reproducibly. Comprehensibility and logical structure still require manual review.
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.
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.
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.
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.
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.
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.