top of page

WCAG

Web Content Accessibility Guidelines

Introduction

The Web Content Accessibility Guidelines (WCAG) define how digital content should be designed so that it can be accessed and used by people with disabilities.

They are the international standard for digital accessibility, used by organizations, governments, and regulatory bodies worldwide.

Most accessibility regulations, including the European Accessibility Act, EN 301 549, RGAA, Stanca Law, and the ADA, rely on WCAG as the technical basis for defining accessibility requirements.

For organizations, WCAG provides a structured and widely recognised framework for implementing accessibility across websites, mobile applications, and digital services.

What is WCAG?

WCAG is a set of guidelines developed by the World Wide Web Consortium (W3C) through the Web Accessibility Initiative (WAI).

It defines how to make:

  • websites

  • mobile applications

  • digital content

  • interactive interfaces

accessible to users with a wide range of disabilities, including visual, auditory, motor, and cognitive impairments.

WCAG does not prescribe visual design. Instead, it defines how content should be structured, presented, and behave, ensuring users can perceive information, navigate interfaces, and complete tasks without barriers.

The guidelines are technology-neutral, meaning they apply regardless of the platform, framework, or programming language used.

WCAG was originally built for the web, so most examples and criteria reflect web content. It can still be applied to mobile and other digital interfaces with some adaptation. Future versions, including WCAG 3.0, are expected to take an even more technology-agnostic approach, making this easier and more consistent.

The four principles of WCAG

WCAG is based on four core principles, often referred to as POUR.

1. Perceivable

Information and user interface components must be presented in ways that users can perceive.

This includes:

  • providing text alternatives for non-text content

  • offering captions and transcripts for multimedia

  • ensuring sufficient colour contrast

  • allowing content to adapt to different screen sizes and zoom levels

Content that cannot be perceived by users cannot be accessed.

2. Operable

User interface components and navigation must be operable.

This includes:

  • full keyboard accessibility

  • logical and consistent navigation structures

  • sufficient time to complete interactions

  • avoiding interactions that rely on precise timing or complex gestures

Interfaces must support different ways of interacting with content.

3. Understandable

Information and the operation of the interface must be understandable.

This includes:

  • consistent navigation and behaviour

  • clear and readable content

  • descriptive labels and instructions

  • meaningful error messages with guidance

Users should be able to understand both the content and how to interact with it.

4. Robust

Content must be robust enough to be interpreted reliably by assistive technologies.

This includes:

  • correct semantic structure in code

  • compatibility with screen readers

  • consistent behaviour across browsers and devices

Robust content ensures long-term accessibility as technologies evolve.

WCAG conformance levels

WCAG defines three levels of conformance, which indicate how thoroughly accessibility requirements are met.

Level A

The minimum level of accessibility.

It addresses basic barriers that prevent access entirely, but does not cover many common usability and interaction issues.

Level AA

The level most commonly required by regulations.

It:

  • provides a balanced level of accessibility

  • is required by standards such as EN 301 549

  • underpins regulations including the European Accessibility Act

Most organizations aim to meet Level AA as a baseline for compliance.

Level AAA

The highest level of accessibility.

It includes more advanced requirements that are not always feasible for all types of content or services.

Level AAA is typically applied in specific contexts, particularly where digital services are designed for audiences in which accessibility is a primary requirement, such as platforms created for people with disabilities.

WCAG versions

WCAG evolves to reflect changes in technology, user behaviour, and accessibility needs.

WCAG 2.0

Published in 2008. It introduced the core structure and principles still used today.

WCAG 2.1

Expanded WCAG 2.0 by adding requirements related to:

  • mobile accessibility

  • low vision

  • cognitive accessibility

This version is widely referenced in current regulations.

WCAG 2.2

Builds on previous versions with additional requirements focused on:

  • improved focus visibility

  • navigation consistency

  • interaction patterns and usability

While many regulations still reference WCAG 2.1, it is recommended to implement WCAG 2.2.

Doing so helps organizations address more recent accessibility needs and reduces the need for future remediation as standards evolve.

How WCAG relates to accessibility laws

WCAG is not a legal framework, but it is used as the technical standard within many regulations.

In Europe

  • EN 301 549 incorporates WCAG requirements

  • the European Accessibility Act relies on EN 301 549

  • national laws such as Stanca Law, BFSG, and BaFG align with WCAG

In the United States

  • the ADA defines legal obligations

  • WCAG is widely used to assess accessibility in legal and regulatory contexts

WCAG provides a common technical reference across jurisdictions.

What WCAG compliance means in practice

Applying WCAG involves ensuring that digital services can be used effectively by people with different abilities across real scenarios.

This includes:

  • navigating interfaces without a mouse

  • using assistive technologies such as screen readers

  • understanding content structure and hierarchy

  • completing tasks such as form submissions, purchases, or bookings

Accessibility must be considered across complete user journeys, including entry points, interactions, and outcomes.

Common accessibility issues covered by WCAG

WCAG addresses recurring accessibility barriers that appear across digital products.

These include:

  • missing alternative text for images

  • insufficient colour contrast

  • inaccessible forms and input fields

  • unclear or inconsistent navigation

  • lack of keyboard support

  • inaccessible documents such as PDFs

  • multimedia without captions or transcripts

These issues often impact usability and user experience more broadly.

Does WCAG guarantee compliance?

Implementing WCAG is a key step toward accessibility, but it does not automatically guarantee compliance with legal requirements.

Regulations may include:

  • accessibility statements

  • documentation and reporting requirements

  • monitoring obligations

  • enforcement mechanisms

WCAG provides the technical foundation, while regulations define how accessibility is assessed and enforced.

How organizations approach WCAG

Organizations typically implement WCAG through a structured and ongoing process:

  1. Assess current accessibility

  2. Remediate identified issues

  3. Integrate accessibility into design and development workflows

  4. Monitor accessibility continuously

Accessibility is most effective when it is treated as an ongoing practice rather than a one-time project.

How Accessiway supports WCAG compliance

Accessiway supports organizations in implementing WCAG through:

  • accessibility audits aligned with WCAG

  • automated accessibility monitoring

  • remediation guidance for development teams

  • accessibility training

  • continuous compliance support

Learn more about how we support accessibility on our solutions page.

These services help organizations align with WCAG, EN 301 549, and accessibility regulations such as the European Accessibility Act and the ADA.

Accessibility becomes more sustainable when it is integrated into everyday digital processes.

bottom of page