Say Aaa: The difference between WCAG A, WCAG AA and WCAG AAA
To determine if your website is accessible, we test it against the Web Content Accessibility Guidelines (WCAG) guidelines. This is the international standard for digital accessibility. There are different versions and levels. We show the differences between WCAG A, WCAG AA and WCAG AAA and which one you should have for an accessible website.
The WCAG standard is developed and managed by the World Wide Web Consortium (W3C). Based on new insights and developments, the WCAG is modified and updated. What does not change is that the WCAG consists of three levels, namely WCAG A, WCAG AA and WCAG AAA. These levels indicate priority based on the impact of the success criterion on accessibility. In addition, lower level A requirements are in general easier to comply with than higher level requirements. But what do these levels mean and which one is most relevant?
Want to know more about the principles WCAG is based on and how to test for compliance? Then check out the article where we show you what WCAG means, how it is structured and how to comply with it. Looking for a specific success criterion? You can find all WCAG criteria on the site of W3C.
Which WCAG level is mandatory?
Which WCAG level must your website or app meet? That is the legally required WCAG AA level. Your website and app must meet the success criteria of both WCAG A and WCAG AA. This is because the WCAG levels are cumulative. Does your site meet this level? Then it is digitally accessible by law. In the Dashboard DigiToegankelijk a website then gets the status A.
WCAG AA is also part of the European accessibility standard EN 301 549. This standard forms the basis of the European Accessibility Act (EAA), which comes into force in 2025.
WCAG A: the basic level
The criteria covered by WCAG A are relatively easy to implement in your website or app. But that does not mean they are less important; quite the contrary. In fact, these success criteria are necessary, because otherwise many people will not be able to use the content. Level A includes 31 success criteria (according to WCAG 2.2).
Examples of these criteria are that the purpose of links is apparent from the anchor text (2.4.4) and that you provide labels or instructions if the user has to provide input (3.3.2). So WCAG A is the bare minimum you must provide, otherwise it is simply impossible for people with disabilities to use your app or website.
WCAG AA: the regulatory level
Level AA goes a step further. Do you want to meet WCAG AA? Then you need to meet not only the 24 criteria of Level AA, but also the success criteria of Level A. If you don't meet Level AA, it will be difficult for people with disabilities to use your app or site.
As you read above, this is the level that websites and apps must meet for the law. So what criteria should you think about? Sufficient contrast, for example, is an important one (1.4.3), so that text is easy to read in relation to the background. Visible focus when navigating via keyboard (2.4.7) is another example.
WCAG AAA: optional success criteria
If your website meets the criteria of WCAG AAA, it will be easier to use for people with disabilities. Without these criteria, this group of people does not encounter insurmountable obstacles. Level AAA includes 31 success criteria above and beyond those of levels A and AA. Thus, it goes beyond the legal requirement.
Meeting these success criteria is difficult. Therefore, in practice you hardly see websites that comply with WCAG AAA. Nevertheless, it is always beneficial if you can meet one or more criteria of WCAG AAA. By doing so, you help people with disabilities.
Want to know more about what it takes to have an accessible website or app? Read what the WCAG means and how to comply. Or what the European Accessibility Act (EAA) means for your business.
