Web Content Accessibility Guidelines (WCAG)
The Web Content Accessibility Guidelines (WCAG) 2.2 cover a wide range of recommendations for making web content more accessible. This includes the accessibility of web content on desktops, laptops, tablets and mobile devices.
All public sector websites must be accessible in order to meet the Public Sector (Websites and Mobile Apps) Accessibility Regulations 2018.
WCAG 2.2 was launched in October 2023 and includes nine additional success criteria since WCAG 2.1. Public sector websites will be tested for compliance with WCAG 2.2 from October 2024.
Web Content Accessibility Guidelines (WCAG) principles
The Web Content Accessibility Guidelines (WCAG) 2.2 have a set of principles designed to help you think about the ways people use web content and how to remove accessibility barriers.
There are 4 principles known as POUR for short:
- perceivable
- operable
- understandable
- robust
Each principle groups a number of WCAG guidelines and success criteria intended to make content accessible for all.
The POUR principles are a good way of understanding the different perspectives of disabled people. They provide a rationale for the guidelines, so you know why they're important and who they impact.
Perceivable
Perceivable means content can be consumed in different ways to suit a person's needs. This could be through sight, hearing or touch. For example, a sighted person will see the content, a blind person may listen to it as synthetic speech and a deafblind person will feel it with their fingertips as electronic Braille.
An example of a perceivable guideline and a success criterion is:
Guideline 1.1 text alternatives
Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
Success criterion 1.1.1 non-text content (Level A)
All non-text content that is presented to the user has a text alternative that serves the equivalent purpose.
Find out more about the WCAG perceivable guidelines.
Operable
Operable means interfaces are usable with a range of input devices such as a mouse or trackpad, keyboards, voice recognition software, switches and more.
This means that regardless of whether you experience content through sight, hearing or touch, you can still interact with it. For example, someone with a physical disability that means they can't use a mouse may use the keyboard or voice recognition instead of a mouse or trackpad.
An example of an operable guideline and a success criterion is:
Guideline 2.1 keyboard accessible
Make all functionality available from a keyboard.
Success criterion 2.1.1 keyboard (Level A)
All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. This applies except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.
Keyboard accessibility is important for people who cannot use a mouse, including people with temporary disabilities such as a broken arm.
Find out more about the WCAG operable guidelines.
Understandable
Understandable means content can be understood by people with different reading needs.
For example, someone who has difficulty reading may want acronyms to be written out in full. If someone is blind, they will want their screen reader to speak foreign language content using the correct accent. If someone has a learning disability, they will prefer things to work consistently wherever they find them.
An example of an understandable principle is:
Guideline 3.1 readable
Make text content readable and understandable.
Success criterion 3.1.1 language of page (Level A)
The default human language of each webpage can be programmatically determined.
Find out more about the WCAG understandable guidelines.
Robust
Robust means content can be handled by whatever user agent a person used. A user agent is software that retrieves and presents web content, for example a browser, assistive technology or media player. This allows people to choose their user agent based on their own needs.
For example, someone with low vision might use Safari on an iOS device with zoom enabled. If someone is blind, they might use Firefox on Windows 10 with the NVDA screen reader. A person who is unable to use a mouse or keyboard might use Internet Explorer on Windows 7 with Dragon voice recognition software.
An example of the robust principles is:
Guideline 4.1 compatible
Maximise compatibility with current and future user agents, including assistive technologies.
Success criterion 4.1.2 name, role and value
For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined. States, properties and values that can be set by the user can be programmatically set. Notification of changes to these items is also available to user agents, including assistive technologies.
Find out more about the WCAG robust guidelines.
Tips
- when planning, creating or testing new content ask yourself if it is perceivable, operable, understandable and robust
- think about the POUR principles and how people with disabilities use the web
Further information
There is a problem
Thanks for your feedback