WCAG Compliance Check – How to Test Your Website

Several legislations, such as the European Accessibility Act (EAA) and the Americans with Disabilities Act (ADA), require your website and app to be WCAG compliant. But how do you check WCAG compliance in a clear and reliable way?

In this guide, we’ll walk you through how to test WCAG compliance using a combination of automated tools and manual testing methods. This will help you confidently assess your current status and take informed next steps.

How to Check WCAG Compliance

To check WCAG compliance, a combination of automated testing and manual review is necessary. Automated testing helps you identify straightforward WCAG violations quickly, while manual review is needed for checks that require human judgment.

Here are the steps to check WCAG compliance:

1. Identify the WCAG version and conformance level you’re testing against
2. Perform automated tests to check for common WCAG issues
3. Conduct manual testing for elements that require human judgment
4. Evaluate the test results to determine your WCAG compliance status

Let’s go through each step in detail.

Step 1: Identify the WCAG version and conformance level

There are multiple versions of WCAG, so the first step is to identify which version (2.1 or 2.2) you’re testing against, and what conformance level applies (A, AA, or AAA). Most checks today are done against WCAG 2.1 Level AA, as it’s the common legal and industry standard.

Step 2: Use automated tools to scan for common WCAG violations

Run automated scans using website accessibility checker tools like WebYes, axe DevTools, or WAVE to quickly identify detectable issues. These tools check for things like low contrast, missing alt text, and structural problems in code, giving you a fast snapshot of compliance gaps.

---

---

Step 3: Conduct manual testing for a comprehensive evaluation

Conduct manual testing to identify accessibility issues that automated tools can’t catch, like focus order and keyboard navigation. You can do this using tools such as Accessibility Insights or by hiring a professional for a comprehensive review.

Step 4: Evaluate the test results to determine your WCAG compliance status

Once you’ve completed both automated and manual testing, review the results against the success criteria for your chosen WCAG version and conformance level. Based on the findings, you can determine whether your website or app is non-compliant, partially compliant, or fully compliant.

What’s Next?

Once you’ve evaluated your WCAG compliance status, the next step depends on your test results.

If you are non-compliant or partially compliant

Work toward fixing all the issues identified during testing. Start with high-impact problems that affect key user interactions, then work your way down the list. Your goal should be to reach full compliance, but at the very least, aim to make your website or app as accessible as possible.

Once you’ve addressed the most critical issues, create an accessibility statement that outlines your current status, what parts are still inaccessible, and your timeline for resolving them. This shows transparency and a clear commitment to improving accessibility.

If you are fully compliant

Great work! But accessibility is an ongoing effort.

Publish an accessibility statement that reflects your current status and outlines how you maintain accessibility over time. Also, set up regular testing checkpoints, especially after content updates or design changes, to ensure your website or app remains compliant as it evolves.

FAQs