From 5d67a55b27e79b3b91e263502b83c3ecc80963f7 Mon Sep 17 00:00:00 2001 From: David Biddle Date: Fri, 10 May 2024 13:58:41 +0100 Subject: [PATCH] Update WCAG wording to reflect the wording in the accessibility regulations Co-authored-by: Andrew Hick <18572857+andrewhick@users.noreply.github.com> --- source/manuals/accessibility.html.md.erb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/manuals/accessibility.html.md.erb b/source/manuals/accessibility.html.md.erb index 8f114a2a..4dcfed9a 100644 --- a/source/manuals/accessibility.html.md.erb +++ b/source/manuals/accessibility.html.md.erb @@ -11,7 +11,7 @@ Government services must be accessible to everyone. This includes anyone with a Building a service with accessibility in mind not only allows those with access needs to use your service, it also improves the service for everyone else. An accessibility problem with a website can be something that affects everyone, not just people who can only access the web with a keyboard or screen reader. -Government services are legally required to be accessible. This means services must comply with the international WCAG 2.2 AA accessibility standard. This requirement applies to all new and existing public sector websites and native applications. +Government services are legally required to be accessible. This means services must comply with the international WCAG 2.2 AA accessibility standard. This requirement applies to all new and existing public sector websites and mobile applications. Further reading: