Skip to content

docs(accessibility): update WCAG references from 2.1 to 2.2 #342

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
RaviK2233 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(accessibility): update WCAG references from 2.1 to 2.2 #342

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions quality-assurance/accessibility-testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Accessibility also benefits people without disabilities, like people with changi

## Legal requirements

We have a legal obligation to make websites and mobile applications conform (as a minimum) to **WCAG 2.1 AA**
We have a legal obligation to make websites and mobile applications conform (as a minimum) to **WCAG 2.2 AA**

The accessibility regulations came into force for public sector bodies on 23 September 2018. They say you must make your website or mobile app more accessible by making it ‘perceivable, operable, understandable and robust’. You need to include and update an accessibility statement on your website.

Expand All @@ -39,9 +39,9 @@ The accessibility regulations build on your existing obligations to people who h

## WCAG (Web Content Accessibility Guidelines)

The Web Content Accessibility Guidelines (known as WCAG 2.1) are an internationally recognised set of recommendations for improving accessibility.
The Web Content Accessibility Guidelines (known as WCAG 2.2) are an internationally recognised set of recommendations for improving accessibility.

WCAG 2.1 is based on 4 design principles:
WCAG 2.2 is based on 4 design principles:

* perceivable
* operable
Expand All @@ -52,7 +52,7 @@ It is the WCAG recommendations that are used to verify whether a website or mobi

Read more about [understanding WCAG](https://www.gov.uk/service-manual/helping-people-to-use-your-service/understanding-wcag).

View the [list of WCAG requirements](https://www.w3.org/WAI/WCAG21/quickref/) (this can be filtered on A level).
View the [list of WCAG requirements](https://www.w3.org/WAI/WCAG22/quickref/) (this can be filtered on A level).

## Developing your service for accessibility

Expand Down
2 changes: 1 addition & 1 deletion quality-assurance/web-accessibility-testing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ You also need to consider cross-browser testing. Unless you are supporting a sin
1. Manual testing using browser plugins against each page of your website. Note the different browsers supported by each.
1. Manual testing using assistive technologies (i.e. screen readers, screen magnifiers and voice control).

Set testing tools to WCAG 2.1 AA standard
Set testing tools to WCAG 2.2 AA standard

## Automated Testing

Expand Down
Loading