Skip to content
    Flow-alerta.cab

    Web Content Accessibility Guidelines (WCAG)

    UX & accessibilityWeb Content Accessibility GuidelinesWCAG 2.1 / 2.2Accessibility Directives
    Editorially reviewed on: 4 sources
    Your reading view

    The short answer · 13 words

    In short

    International standard of the W3C with concrete criteria for accessible, accessible web content.

    Flow-alerta.cab (2026): Web Content Accessibility Guidelines (WCAG). https://flow-alerta.cab/en/glossar/wcag. Editorially reviewed on: 09 October 2026.

    How much detail would you like?

    Practical

    Important basis for digital accessibility. Which legal obligations apply depends on the offer and the relevant regulations.

    Possible example: An online shop adapts color contrasts, stores descriptive old text for product images and produces complete keyboard usability.

    Possible application: Examine requirements for usability, contrasts, text alternatives and structure; determine the legal obligations for the specific offer separately.

    At a glance

    Core
    The Web Content Accessibility Guidelines (WCAG) define technical and design criteria at conformity levels A, AA and AAA. They are based on four principles: perceptibility, usability, comprehensibility and robustness.
    Use
    Important basis for digital accessibility. Which legal obligations apply depends on the offer and the relevant regulations.
    Example
    Possible example: An online shop adapts color contrasts, stores descriptive old text for product images and produces complete keyboard usability.
    Limits
    Check WCAG only shortly before launch; confuse AA compliance level with purely automatic scans; lack of semantic heading hierarchy; keyboard focus not visible.

    In context

    Accessibility

    Accessibility makes digital content usable for as many people as possible.

    Accessibility

    Accessibility makes digital content usable for as many people as possible.

    Questions about this term

    Is WCAG AA a statutory requirement for every company?

    No, applicable requirements depend on the offer and its legal framework.

    Are Automatic Testing Tools Enough?

    No, they cannot evaluate all aspects; human trials are additionally required.

    All details and background

    The Web Content Accessibility Guidelines (WCAG) define technical and design criteria at conformity levels A, AA and AAA. They are based on four principles: perceptibility, usability, comprehensibility and robustness.

    ELI5 – Explained simply

    Like a catalogue of verifiable rules, so that web content can be used, for example, with a keyboard or screen reader.

    Why it matters in practice

    Important basis for digital accessibility. Which legal obligations apply depends on the offer and the relevant regulations.

    Example

    Possible example: An online shop adapts color contrasts, stores descriptive old text for product images and produces complete keyboard usability.

    Pitfalls and limits

    • Check WCAG only shortly before launch; confuse AA compliance level with purely automatic scans; lack of semantic heading hierarchy; keyboard focus not visible.

    Origin & history

    The WCAG have been further developed over several versions: WCAG 2.0 was published in 2008, 2.1 in 2018 and 2.2 in 2023. The specific test shall specify the version and the level of conformity.

    Use in mid-sized companies

    • Possible application: Examine requirements for usability, contrasts, text alternatives and structure; determine the legal obligations for the specific offer separately.

    Related terms

    Matching Flow-alerta service

    Websites & web applicationsWebsites & web applications

    Matching tool / use case

    View use casesPossible Use Case: Examine a website against a named WCAG version and level with automated helps and manual operator control tests.

    Sources

    Quellen geprüft am 09.10.2026. Redaktionelle Anwendungsbeispiele sind hypothetisch; kein Nachweis realer Kundenergebnisse.

    Editorially reviewed on:

    Next step

    Put knowledge into practice

    Discuss your projectView use cases