QF-Test provides ready-made procedures for accessibility tests.
On the one hand, websites can be tested using an integrated library for accessibility tests, axe-core. The comprehensive functionality of axe-core can be used from within QF-Test without any programming effort and can be fine-tuned using various parameters. Custom test protocols and the highlighting of faulty components make working with axe-core easier.
On the other hand, QF-Test offers its own accessibility tests that go beyond the possibilities of axe. A separate color contrast check for graphical elements is already included in the current version, further checks, such as checking whether the focus of elements is visible, will follow in future versions.
Of course, QF-Test can also be used to create your own accessibility tests with its options for simulating user interactions and deep access to the websites to be tested.
Special webinar: Web Accessibility Testing with QF-Test
By June 28 of this year, business websites within the EU must be accessible.
But what does accessibility mean in a web context? What do providers have to pay attention to?
And above all: How can QF-Test support you in meeting the legal requirements?
In this webinar, we will give a brief introduction to web accessibility and present the new accessibility testing features of QF-Test.
This video shows you the new features of QF-Test 9, including how to automatically test websites for accessibility.
You can find more information on accessibility testing in the manual
QF-Test provides software development and testing teams with a reliable, powerful tool for accessibility testing.
With the automated accessibility testing tool QF-Test, testers receive precise evaluations with tips on how to resolve any problems found. Our test reports in HTML format are flexible and interactive.
See for yourself in our interactive sample report: Scroll down, enlarge screenshots and messages with one click, use the arrow keys to navigate quickly between entries.
QF-Test offers a powerful and easy-to-integrate solution for accessibility testing. With the accessibility testing tool QF-Test, software testers and developers can efficiently perform automated accessibility testing and ensure that their websites comply with current standards.
Use QF-Test and make your website or web application accessible for all!
In an increasingly digital world, web accessibility ensures that digital content is accessible to everyone. In addition to their social responsibility, companies benefit from a better user experience and an expanded target group. Accessibility is also becoming increasingly relevant for compliance with legal regulations such as the EU Directive (EU) 2019/882 of the European Parliament and theEuropean Accessibility Act that comes into force on June 28, 2025.
A central element of digital accessibility is the support of assistive technologies such as screen readers, Braille displays or voice controls. These technologies enable people with disabilities to use web applications effectively. It is therefore essential that websites are compatible with these assistive technologies. Even people who are less tech-savvy benefit from web accessibility
How do companies and development teams manage to design digital products that are truly accessible to everyone?
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 extremely time-consuming. Automated accessibility tests or A11y tests 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 display 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 aspects by performing automated tests in accordance with the Web Content Accessibility Guidelines (WCAG) 2.1.
The accessibility testing tool QF-Test also offers the option of categorizing test results. Errors and warnings are systematically recorded and presented in interactive reports that contain information on how to resolve them. This facilitates the prioritization of measures and supports software development teams in continuously improving the accessibility of their web applications.
To ensure that systems and applications can also be used by people with disabilities, there are internationally recognised standards and guidelines. These define standards and criteria that influence test processes and development decisions. Compliance with these guidelines is not only a legal obligation for many organisations, but also a contribution to inclusive design. Software testers and developers can use these standards to ensure that their applications meet the needs of all users. Below you will find the most important standards and their focal points.
WCAG form the basis for accessible web content worldwide. They are divided into three conformance levels: A, AA and AAA, with AA being the standard for many applications. The guidelines provide detailed specifications on how content can be made accessible for people with different disabilities.
This standard is particularly important for Europe. It defines requirements for the accessibility of information and communication technologies (ICT) and is based directly on the WCAG. EN 301 549 is particularly mandatory for public organisations in the EU. It comprises the four principles of perceptibility, usability, comprehensibility and robustness.
In order to create a clear framework for web accessibility within the European Union (EU), the European Parliament and the Council of the EU adopted Directive 2016/2102 "on the accessibility of the websites and mobile applications of public sector bodies" in 2016. The directive attempts to make the web and app representation of public services within the EU more accessible and to harmonise the varying standards within the member states. It is the first directive to include web accessibility as a key issue.
In Germany, the BITV 2.0 implements the WCAG guidelines at national level. It stipulates that websites and mobile applications of public bodies must be accessible and serves as a benchmark for the implementation of EU Directive 2016/2102.
The most important difference to EU Directive 2016/2102 is the scope of the stakeholders required by this law to comply with accessibility regulations: In the EAA, this applies not only to public authorities, but also to companies. Companies within the EU must fulfil the measures required by the EAA by the end of June 2025.
The BFSG defines the "accessibility requirements for products and services" within Germany, as well as the sectors and companies affected.
The international standard ISO 9241-171 provides specific recommendations for the design of accessible interactive systems. It is particularly interesting for software developers and testers who want to develop ergonomic and accessible user interfaces.
Testing accessibility is becoming an essential part of modern software development. Manual and automated testing procedures, which include both manual and automated test steps, are used. Both approaches have their specific strengths and challenges and play an important role in the testing process.
Manual tests are essential to comprehensively assess the accessibility of software. They enable a human assessment of the structure, content and usability that automated testing tools alone cannot provide.
Manual tests allow usability and operability to be assessed from the perspective of affected persons. With the help of tools such as screen readers, magnification software or keyboard navigation, testers can check the actual usability of the software. They also identify more subtle problems that automated testing tools may overlook, such as the logical structure of content or the comprehensibility of instructions. Manual tests are particularly helpful when evaluating dynamic content and complex user interfaces that are difficult to analyse with automated test steps.
Manual testing requires a high level of experience and expertise - a deep understanding of the needs of people with disabilities and the ability to assess the software from their perspective. The process can be time-consuming, require significant human resources and is prone to subjective judgement. The results can therefore vary depending on the tester, which can affect the consistency of the test. It is also difficult to cover all aspects of accessibility using purely manual methods. The use of screen readers or keyboard navigation is necessary to check accessibility for users with visual or mobility impairments, but they are essential to evaluate the software from the perspective of real users and ensure that accessibility is not only technical but also practical.
Automated tests complement manual procedures and are an important part of accessibility testing. They enable fast, scalable and repeatable analysis of technical aspects of the software.
Accessibilty testing automation is ideal for identifying technical errors such as missing alt texts, faulty ARIA roles or insufficient colour contrasts. With a suitable accessibility testing tool like QF-Test, large amounts of data can be analysed in a short time and enable scalable testing of large software projects. Accessibility testing automation steps are also ideal for continuously checking accessibility in the development process and ensuring that new changes do not violate existing standards and that potential problems are recognised at an early stage. They deliver reproducible results and minimise subjective influences.
The combination of manual and automated test steps ensures a holistic accessibility check. While manual testing is essential to evaluate the actual user experience and analyse complex interactions, the key to efficiency lies in automation.
Automated accessibility testing tools make it possible to integrate accessibility checks quickly, scalably and continuously into the development process. They relieve test teams of recurring test steps and ensure that technical requirements are systematically monitored.
Especially in agile projects, where software changes in short cycles, automated checks are an indispensable tool for ensuring quality in the long term. Only through their targeted use can resources be optimally utilised and accessibility efficiently integrated into software development.
report their
QF-Test experiences
report their
QF-Test experiences
report their
QF-Test experiences
