What is the WCAG?

To be digitally accessible as a business or organization, you must comply with international guidelines: the Web Content Accessibility Guidelines (WCAG). You can find everything about the WCAG guidelines for digital accessibility here.

The WCAG: the handbook for digital accessibility

As a government, business or supplier, you are getting started with digital accessibility. But, where do you start? One of the most important aspects of digital accessibility is applying the WCAG 2.2. Think of these guidelines as the best handbook for digital accessibility.

What is the WCAG?

The WCAG stands for Web Content Accessibility Guidelines. In other words, guidelines for digitally accessible content. The WCAG were written primarily for websites. Meanwhile, they are also used for accessible design and construction of:

The different variants of the WCAG

The WCAG 2.1

The WCAG 2.1 AA is the current legal standard for the Digital Government Act. This variant consists of 50 success criteria at level AA.

All about WCAG 2.1

The WCAG 2.2

WCAG 2.2 was published on 5 October 2023. This version adds 6 new criteria. All our surveys are based on the WCAG 2.2 AA.

All about the WCAG 2.2

The WCAG 3.0

WCAG 3 is currently under development. It is still entirely a concept. Only in a few years' time will it become the new standard for digital accessibility.

All about the WCAG 3.0

How is the WCAG structured?

1. Layers, layers, layers

The WCAG is made up of several layers:

  • 4 principles

  • 13 guidelines

  • 87 success criteria

2. Different levels

In doing so, the WCAG is made up of different levels:

  • Level A

  • Level AA

  • Level AAA

These levels are built up in ‘difficulty’. The higher the level, the more difficult it is to apply. In doing so, they are based on making websites more accessible to people with specific disabilities.

3. Different versions

Just like an iPhone (8, 10, 12, 14...), WCAG has a range of versions. Each version is a little bit better each time. For example, you have the:

The 4 principles and 13 guidelines

Principle 1: Perceptible

Websites should be easily perceivable by all users. Consider sufficient colour contrast of texts, and the presence of text alternatives to images.

These are the corresponding guidelines:

  • Provide text alternatives for non-textual content.

  • Provide a transcript for audio and video content.

  • Provide video content with subtitles.

  • Make sure content is logically structured.

  • Use semantic (meaningful) code.

  • Make sure each feature can be used when the default text size is doubled.

2. Operable

Websites should be easily operable, e.g. by keyboard, mouse, touch, voice control, a joystick or eye-tracking.

These are the corresponding guidelines:

  • Make sure everything works with a keyboard.

  • Show keyboard focus.

  • Use descriptive titles for pages and windows.

  • Use descriptive links so it is clear where it leads.

  • Do not use flashing content.

3. Understandable

Websites must be understandable: the structure and texts must make sense to everyone. For example, the language of the page must also be able to be read by auxiliary software.

These are the corresponding guidelines:

  • Give software the ability to determine the language of the page.

  • Make the text readable and understandable.

  • Make sure all form fields have visible and meaningful labels.

  • Make it easy to recognise incorrect entries in forms.

4. Robust

Websites should be robust. The technology behind the website must be good and ensure that auxiliary devices can also use the website properly.

Here are the corresponding guidelines:

  • Use error-free code.

  • Ensure maximum compatibility with current and future browsers and other utilities.

  • Make sure assistive technologies understand what each function is for and its state.

87 success criteria

Measurable requirements

These are the actual measurable requirements that accessible content must meet. An example is the minimum colour contrast of text on a background.

Split between content and technology criteria

In our WCAG audits, we split content and technique in some situations. You can read all the criteria of the WCAG detail in our checklist.

Download the WCAG checklist

The levels

Level A

The bare minimum that websites must meet. There are 31 success criteria at the lowest level. These are easier to apply.

Level AA

This is the desired level that websites and apps must meet according to European and Dutch regulations. There are 24 success criteria at level AA.

Level AAA

These are 31 Level AAA success criteria and are not legally required. However, they can help you make websites even more accessible to people with specific disabilities.

The development of WCAG

  1. 5 May 1999 - WCAG 1.0

    The first version of WCAG has been published (WCAG 1.0). This version was mainly focused on HTML.

  2. 11 December 2008 - WCAG 2.0

    The WCAG 2.0 published. This version took into account a wide range of technologies and helps developers create digitally accessible content. It also established the four principles.

  3. 5 June 2018 - WCAG 2.1

    WCAG 2.1 published with 17 new success criteria. Many of the new success criteria address accessibility issues that arose as mobile browsing became increasingly popular.

  4. 7 September 2018

    WCAG 2.1 at level AA included in the European standard EN 301 549. This means that WCAG 2.1 AA is guiding legislation.

  5. 23 September 2022

    All Dutch government websites must comply with WCAG.

  6. 23 June 2021

    All government apps must also comply.

    • App audit

      Audit your app and get an accessibility declaration report.

  7. 5 October 2023

    WCAG 2.2 has been published! This new version must first be incorporated into the European standard EN 301 549.

    • WCAG 2.2 audits

      Use our WCAG audits to get a clear picture of how accessible your website, app or PDF document is.

    • Trainings

      Take one of our accessibility training courses and become a specialist in digital accessibility.

The benefits of the WCAG!

You now know more about the WCAG, but: when is your website really WCAG compliant? A website is WCAG-proof if you meet all 55 success criteria at level A+AA of the Web Content Accessibility Guidelines. This has a lot of extra benefits.

  • You reach 25% more users. The Netherlands has about 4,000,000 people with functional disabilities.

  • Your website is more usable with different browsers and platforms.

  • Your website is flexible and durable, making it easy to reuse or replace elements.

  • Your website scores higher on usability.

  • Your website will be better found by search engines (SEO/Google).

The WCAG and legislation

The WCAG is mandatory for Dutch public authorities (such as provinces, municipalities and water boards) and institutions in the (semi-)public sector. The websites of these organisations must at least comply with WCAG 2.1 AA at levels A and AA. This has been the case since 2018. But now it is also in the Digital Government Act.

The same applies to the European Accessibility Act. For this, most likely the WCAG 2.2 guidelines will be the standard.

The future of WCAG?

On 5 October 2023, WCAG 2.2 was published by the W3C as the new recommended standard for digital accessibility. For now, nothing will change for Dutch government organisations. The new version must first be incorporated into the European standard EN 301 549.

In WCAG 2.2, six new success criteria at level A and AA are added (+ 2 at level AAA). This version is not yet the standard, but we are already testing for these new criteria.

WCAG 3.0

Meanwhile, work is also underway on WCAG 3. The first draft of this has already been published, but we do not expect the final version in the next few years. WCAG 3 will provide a completely new set of guidelines, the 3 levels (A, AA and AAA) will disappear and there will be a new ‘calculation’ for the new score. With the advent of WCAG 3, version 2 will eventually be dropped. Because WCAG 3 does not only focus on ‘web content’, the abbreviation will also have a different meaning: WCAG 3 = W3C Accessibility Guidelines.

Download the WCAG checklist

Do you want to get started with the WCAG 2.2 AA success criteria yourself? Then leave your name and e-mail address and download our WCAG checklist. Then you can get started right away!

Name is missing.
Email is missing.
Send me the latest updates on digital accessibility.
Marijn van der Laan

We help you with the WCAG

Do you want to know whether your website or app already complies with WCAG? Then request a WCAG audit to have your website or app examined for the Web Content Accessibility Guidelines.

  • Complete WCAG 2.2 audit

    Complete audit according to WCAG-EM, based on WCAG 2.2, level AA.

  • Technical audit

    Do you want to develop your platform digitally accessible? Then opt for a technology study.

  • Content audit

    Ideal if a full WCAG audit is not needed. We figure this out together.

  • Quick scan

    Get a first impression of your website’s digital accessibility.

  • App audit

    Audit your app and get an accessibility declaration report.

  • PDF audit

    Check how accessibly your PDF documents are formatted

  • Additional audit

    Perfect for after a major update or new functionality on your website, app or PDF document.

Interesting articles about the WCAG

All blog articles

Questions about the WCAG?

Like Carolina, do you get raving about the WCAG? Or are you just at a loss for words? Contact us and we will be happy to help you further along the way.

Message is missing.
First name is missing.
Last name is missing.
Email is missing.
Send me the latest updates on digital accessibility.
Carolina van Setten, Brand Manager Cardan