Need testing support? Check our Quality Assurance services.

Read also: Automated vs. Manual Testing in 2026: Where Does AI Change t

Let’s discuss your project

“Testing shows the presence of defects, not their absence.”

— ISTQB, ISTQB Certified Tester Foundation Level Syllabus v4.0 | Source

Have questions or need support? Contact us – our experts are happy to help.

In an era of digital transformation, website accessibility has become a key element of software development. It’s no longer just a matter of meeting regulatory requirements or industry standards - it’s a fundamental aspect of designing modern web applications. This comprehensive guide will walk you through the process of testing accessibility according to WCAG guidelines, from basic concepts to advanced implementation strategies. You’ll learn how to effectively get started with WCAG, what tools to use, and how to integrate accessibility testing into your software development cycle.

What is WCAG and why is it so important in accessibility testing?

WCAG (Web Content Accessibility Guidelines) is an international standard that defines how web content should be accessible to people with various disabilities. The standard was developed by the World Wide Web Consortium (W3C) as part of the WAI (Web Accessibility Initiative) and is regularly updated to meet the challenges of changing technology.

The importance of WCAG goes far beyond the legal or regulatory compliance aspect. In fact, the implementation of WCAG guidelines translates into real business benefits. WCAG-compliant websites reach a wider audience, which can directly increase conversion and user satisfaction.

It is also worth noting that accessibility according to WCAG is not limited to people with disabilities. For example, clear text and well-organized navigation improve the usability of the site for all users, including the elderly or those using mobile devices in difficult lighting conditions.

What are the basic levels of WCAG compliance?

The WCAG standard defines three levels of compliance: A, AA and AAA, where each successive level increases the accessibility requirements. Level A is the basic foundation of accessibility and covers the criteria that must be met for a site to be considered accessible at all.

Level AA is now considered the standard for most commercial and government projects. It includes all the requirements of Level A, plus additional criteria that significantly improve the accessibility of the site. This level requires, among other things, the provision of adequate color contrast and subtitles for audio content.

The highest AAA level introduces the most stringent requirements, which can be difficult to meet for certain types of content. It includes, for example, the provision of sign language translation for all video content or the ability to adjust the spacing between lines of text.

It is worth noting that the choice of the appropriate compliance level should be dictated by the specifics of the project, legal requirements and the needs of the target user group. It is not always necessary to aim for the highest AAA level - sometimes a solid compliance with AA level requirements is sufficient.

What do the four main WCAG principles cover?

WCAG is based on four fundamental principles that form the acronym POUR: Perceivable, Operable, Understandable and Robust. These principles are not just theoretical concepts - they are the practical foundation on which the entire philosophy of digital accessibility rests. Each of them addresses specific user needs and is crucial to the overall accessibility of a website.

Perceivability requires that information and user interface components be presented in a way that can be perceived by all users. Among other things, this means providing alternative texts for non-text content, customizable content presentation, and appropriate information structure.

Functionality focuses on ensuring that all interface and navigation elements can be operated by different users. The key here is to allow full keyboard operation of the site, to provide sufficient time to complete tasks, and to avoid content that may cause epileptic seizures.

Understandability applies not only to the content itself, but also to the way the user interface works. The site should be predictable in operation, and all forms and interactions should include clear instructions and effective error handling.

How do you prepare to start accessibility testing?

Effective accessibility testing requires proper preparation and a systematic approach. The first step is to carefully read the WCAG guidelines and understand how they translate into specific test cases in the context of our application.

A key element of preparation is to create a comprehensive testing strategy that takes into account various aspects of accessibility. It is important to determine which elements will be tested manually and which can be automated. It’s also a good idea to create a checklist that includes all WCAG success criteria that apply to our project.

It is also important to understand different usage scenarios and the needs of different user groups. It is worth conducting research on typical problems that people with different disabilities encounter when using similar applications. This will help better target our testing efforts.

What tools are necessary for WCAG testing?

In the process of accessibility testing, it is crucial to use the right set of tools, both automatic and to support manual testing. The basic tool is a browser-based code inspector, which allows analysis of HTML structure and accessibility attributes.

Automated testing tools, such as WAVE, aXe or Lighthouse, can quickly identify basic accessibility issues. However, keep in mind that no automated tool can detect all accessibility issues - some aspects require human judgment.

Screen readers, such as NVDA or VoiceOver, are also indispensable for experiencing a site in a maer similar to blind people. In addition, tools for testing color contrast, simulators for different types of daltonism or tools for testing keyboard navigation are important additions to the accessibility tester’s arsenal.

How to conduct exploratory accessibility testing?

Exploratory testing in the context of accessibility requires a specific approach, combining systematicity with creativity. A key element is to take the perspective of different user groups and understand how they might interact with the application under test.

During exploratory testing, it is a good idea to start with a general overview of the site, paying attention to the basic interface elements and their accessibility. Check that all functionality is accessible without using the mouse, that information is presented in a logical and understandable ma

er, and that the site structure is consistent.

An important aspect of exploratory testing is to document the problems found in a way that will allow for later reproduction and repair. It is a good idea to create detailed descriptions of the steps leading up to the problem, along with information about the test environment and the supporting tools used.

How do you test accessibility using a keyboard?

Keyboard accessibility testing is a fundamental part of WCAG compliance verification. Verify that all interactive elements of the site are accessible and operable by keyboard, with particular attention to tab order.

During testing, special attention should be paid to the visibility of the keyboard focus - each active item should have a clear visual indication when the focus is on it. This aspect is crucial not only for users with motor limitations who rely solely on keyboard navigation, but also for those using various assistive technologies and users who prefer keyboard navigation for its efficiency.

Another important aspect is to check for so-called “keyboard traps” (keyboard traps) on the site, i.e. situations where the user caot exit a specific interface element using only the keyboard. This is especially true for modal dialog boxes and drop-down menus.

How to effectively use screen readers in testing?

Testing with screen readers requires not only technical knowledge of the tool, but also an understanding of how blind and visually impaired people use assistive technologies. It’s a good idea to start with basic usage scenarios, such as navigating through the main sections of a page or filling out forms.

During testing, special attention should be paid to HTML semantics and correct use of ARIA tags. The screen reader should convey all relevant information to the user in a logical order, with proper context. It is especially important to check that dynamically changing content is correctly a

ounced by the reader.

Testing with a screen reader should also include verification that all error messages and acknowledgments are properly read, and that the user receives sufficient information about the status of operations being performed. It is also worth verifying that decorative content is properly ignored by the reader.

What are the key elements of contrast and color testing?

Contrast and color testing is not only a matter of aesthetics, but more importantly, functionality and accessibility of the site for people with various forms of visual impairment. The basic requirement is to ensure adequate contrast between text and background, according to the WCAG guidelines for the chosen level of compliance.

In the testing process, use specialized contrast measurement tools that allow you to accurately determine the contrast ratio for different interface elements. Special attention should be paid to texts of smaller size and interface elements that can change their appearance in different states (e.g., buttons when hovering the mouse).

It is also important to check that information is not conveyed solely through color. All important visual cues should be supplemented with alternative methods of conveying information, such as icons, patterns or text. It’s also a good idea to test the site in different display modes, including high-contrast mode.

How to test alternative texts for graphic elements?

Testing alternative texts requires not only a technical verification of their presence, but, above all, an assessment of their quality and suitability for blind users. A good alternative text should convey the same information or create the same impression as a graphic element for sighted people.

For decorative images that do not carry any relevant information, make sure that they are properly marked as skip elements by screen readers. This can be accomplished by using an empty alt="" attribute or an appropriate ARIA tag. This is just as important as providing proper descriptions for informational images, as it avoids u

ecessary information noise.

Special attention should be paid to testing alternative texts for complex graphics, such as charts or infographics. In such cases, it is often necessary to provide a more elaborate description, which can be implemented in a variety of ways - through extended alternative text, aria-describedby or a dedicated, visually hidden piece of text containing a detailed description.

How to verify the structure of headings and navigation?

Proper header structure is the foundation of an accessible website, allowing screen reader users to effectively navigate content. When testing, make sure the header hierarchy is logical and complete, starting with a single h1 header and then moving to appropriately nested lower-level headers.

It’s worth using tools that allow you to visualize the structure of headings, such as browser extensions that show the outline of a document. This allows you to quickly identify hierarchy problems, such as jumping heading levels or lack of proper section structure. It is also important to check that headings properly describe the content of the sections they introduce.

Navigation testing should include verification of the availability of all menus and navigation lists, both main and side menus. Particular attention should be paid to whether the navigation structure is consistent throughout the site and whether users can easily skip repetitive navigation blocks.

How to conduct form accessibility testing?

Form accessibility testing requires a comprehensive approach, including both technical and usability aspects. Each form field should be correctly associated with a label using the label element or the corresponding ARIA attributes. This is a basic requirement that should be verified first.

An important element is to check that all form fields convey the appropriate information about their status and requirements. Users should be informed about mandatory fields, restrictions on data input, and receive clear error messages. This information must be available not only visually, but also to screen reader users.

When testing forms, attention should also be paid to the order of focus, which should be logical and intuitive. It is worth checking that the user can easily move between fields using the keyboard, and that they have the ability to return to fields containing errors after trying to submit the form. It is especially important to test complex form components, such as auto-complete fields or date selectors.

What are the most common WCAG testing mistakes?

One of the most common mistakes in accessibility testing is over-reliance on automated tools. While they are extremely useful in detecting basic problems, they are unable to assess the contextual accuracy of many elements, such as the quality of alternative texts or the logicality of the navigation structure. Effective testing requires a combination of automation and thorough manual verification.

Another common mistake is to skip testing with actual assistive technologies. Mere simulation or theoretical knowledge of WCAG requirements is no substitute for experience with the actual operation of screen readers or other assistive tools. It is worthwhile to involve people with experience in using these technologies in the testing process.

How to interpret the results of accessibility tests?

Interpreting accessibility test results requires a holistic approach and an understanding of the context in which the problems found occur. Not all violations of the WCAG guidelines are of equal severity - some may completely prevent certain user groups from using the site, while others represent only a minor impediment.

When analyzing the results, it is useful to categorize the problems found not only according to WCAG compliance levels (A, AA, AAA), but also according to their real impact on users. Consider factors such as the number of users likely to be affected, the frequency of the problem, and its impact on key site functionality. This will help you prioritize when planning repairs.

An important aspect of interpreting the results is also to analyze patterns in the problems found. Often similar errors are repeated in different parts of the site, which can indicate systemic problems in the development or design process. Identifying such patterns helps develop long-term solutions and prevent similar problems in the future.

How to prepare a professional accessibility test report?

A professional accessibility testing report should not only be accurate and complete, but also understandable to a variety of audiences - from the developers who will be fixing the problems found, to the managers making decisions about priorities and resource allocation. It is worth including in the report a detailed description of the testing methodology, the tools used and the scope of the tests performed.

For each problem identified, the report should include a precise description with reproduction steps, a reference to the specific WCAG guidelines that were violated, and suggested solutions. It is particularly valuable to include examples of best practices or specific code snippets that show how the problem can be fixed.

An important element of the report is also the executive summary section, which succinctly presents the most important findings and recommendations. This section should include information on the overall level of accessibility of the site, the most serious problems found, and a suggested corrective action plan with estimated workload.

How do you automate accessibility testing?

Automating accessibility testing requires a thoughtful approach and an understanding of the limitations of automated tools. A good starting point is to integrate basic accessibility testing into a continuous integration (CI/CD) process, which allows early detection of the simplest problems as early as the development stage.

In the automation process, it is worthwhile to use different testing tools and libraries that offer different perspectives and testing capabilities. For example, combining static code analysis tests with dynamic tests performed in the browser can provide broader coverage of various aspects of accessibility. However, keep in mind that even the best automated tools can only detect about 30-40% of potential accessibility issues.

A key element of automation is the proper configuration of acceptance thresholds and reporting of results. It is worth defining which accessibility violations should block the deployment process, and which can only be reported for later analysis. It’s also important to provide clear reports on automated tests to help developers quickly identify and fix problems.

How to combine manual and automated testing for best results?

An effective accessibility testing strategy requires a skillful combination of manual and automated tests. Automated tests are excellent for quickly detecting basic technical problems, such as missing alt attributes or incorrect ARIA relationships, while manual tests are essential for assessing qualitative and contextual aspects.

A good practice is to start with automated testing as the first line of defense, and then supplement it with detailed manual testing in key areas of the application. It’s a good idea to create a schedule of regular manual tests that focus on checking aspects of accessibility that can’t be automated, such as the logicality of navigation or the understandability of messages.

What are the latest changes to the WCAG standard?

The WCAG standard is constantly evolving to keep up with developments in web technology and changing user needs. The latest versions of the standard place particular emphasis on the accessibility of mobile content and Single Page Application (SPA) applications. New guidelines have been introduced for touch interaction, gestures, and support for different screen orientations, which is particularly important in the context of mobile devices.

Criteria for accessibility of multimedia content are also a significant area of development. The new guidelines clarify requirements for live captioning, audiodescription and transcription for different types of media. This is in response to the growing popularity of video and audio content on the Internet, which must be accessible to all users.

Recent WCAG updates have also placed greater emphasis on the cognitive aspects of accessibility. New criteria have been introduced for readability of content, predictability of the interface, and aids to navigation. These changes reflect a growing awareness of the needs of people with various forms of cognitive disabilities.

How to adapt the testing strategy to different WCAG levels?

Adapting a testing strategy to different levels of WCAG compliance requires a thoughtful approach and proper distribution of emphasis. When testing at Level A, the focus should be on basic accessibility aspects that are crucial to the basic usability of the site. This includes, but is not limited to, alternative text for images, keyboard accessibility and basic header structure.

Testing at the AA level requires expanding testing to include more advanced aspects of accessibility. At this level, special attention should be paid to color contrast, responsiveness, subtitling for audio content and support for assistive technologies. It is worth remembering that AA level is now considered the standard for most commercial projects.

When aiming for AAA-level compliance, the testing strategy must address the most stringent requirements. Testing at this level should include advanced aspects of accessibility, such as sign language translation, enhanced audiodescription or the ability to adjust text spacing. However, it is important to remember that not all AAA level criteria are possible to meet in every project.

How to integrate accessibility testing into the software development process?

Successfully integrating accessibility testing into the software development process requires a systemic approach and the involvement of the entire project team, from UX designers to developers and testers. It is crucial to introduce accessibility testing early in development - during interface design and application architecture - rather than treating it as an add-on at the end of the process. This shift-left in accessibility testing saves significant time and money, as it is always more costly to make changes at later stages of a project. The foundation of this approach should be training and building awareness within the team about the importance of accessibility and its impact on end users.

A practical solution is to introduce accessibility checklists into the code review process. This allows you to catch basic accessibility issues even before the changes are integrated into the main branch of the project. Additionally, consider introducing automated accessibility testing as part of the CI/CD pipeline.

It is also important to conduct accessibility audits on a regular basis and include users with disabilities in the testing process. Their perspective and experience are invaluable in identifying real accessibility issues. It is also worth considering creating a dedicated accessibility specialist role on the team to coordinate all WCAG compliance activities.

In summary, accessibility testing according to WCAG guidelines is a complex process that requires a systematic approach. The key to success is a combination of different testing methods, regular verification of compliance and continuous improvement of the process based on lessons learned. Let’s remember that accessibility is not only about compliance with standards, but first and foremost about making the Internet really easy to use for all users.

How ARDURA Consulting supports testing and quality assurance

Effective testing requires skilled QA engineers who know the latest tools and methodologies. ARDURA Consulting, with a network of over 500 senior IT specialists and 211+ completed projects, provides experts ready to start within 2 weeks — with 99% retention rate and 40% cost savings compared to traditional hiring.

Need support? Contact us — we’ll help you find the right specialists for your needs.

See also