Make sure any 'action links' are at least 24px by 24px in size, with adequate spacing. This is to make sure users can easily interact with the links. This relates to WCAG 2.2 success criterion 2.5.8 Target Size (minimum).
diff --git a/src/patterns/confirmation-pages/index.md b/src/patterns/confirmation-pages/index.md
index c80a852567..b9356f516e 100644
--- a/src/patterns/confirmation-pages/index.md
+++ b/src/patterns/confirmation-pages/index.md
@@ -9,35 +9,9 @@ layout: layout-pane.njk
---
{% from "_example.njk" import example %}
-{% from "govuk/components/inset-text/macro.njk" import govukInsetText %}
-{% from "govuk/components/tag/macro.njk" import govukTag %}
Use this pattern to let users know they’ve completed a transaction.
-{% set wcagCallout %}
-
-{{ govukTag({
- text: "WCAG 2.2",
- classes: "app-tag"
-}) }}
-
-### New WCAG 2.2 criteria affects this pattern
-
-To use ‘Confirmation pages' and meet the new Web Content Accessibility Guidelines (WCAG) 2.2 criteria, make sure that users can successfully:
-
-- [see and understand text in the green confirmation panel](/patterns/confirmation-pages/#wcag-see-understand-text)
-- [select and copy text within a confirmation page as well as its panel](/patterns/confirmation-pages/#wcag-select-copy-confirmation)
-
-See the full list of [components and patterns affected by WCAG 2.2](/accessibility/WCAG-2.2/#components-and-patterns-affected-in-the-design-system).
-{% endset %}
-
-{{ govukInsetText({
- html: wcagCallout,
- attributes: {
- style: 'border-left-color: #1d70b8;'
- }
-})}}
-
Include a link to the [GOV.UK feedback page](https://www.gov.uk/service-manual/service-assessments/get-feedback-page) to allow users to tell you what they think of your transaction.
{{ example({ group: "patterns", item: "confirmation-pages", example: "default", html: true, nunjucks: true, open: false, size: "xl", loading: "eager" }) }}
@@ -59,15 +33,7 @@ Your confirmation page must include:
- a link to your [feedback page](https://www.gov.uk/service-manual/service-assessments/get-feedback-page)
- a way for users to save a record of the transaction, for example, as a PDF
-
- {{ govukTag({
- text: "WCAG 2.2",
- classes: "app-tag"
- }) }}
-
Do not include links, buttons or other interactive elements in the green confirmation panel, as the focus state will not have a minimum contrast ratio of 3:1 with the panel’s background colour.
-
-
-{{ example({group: "patterns", item: "confirmation-pages", example: "default", html: true, nunjucks: true, open: false, titleSuffix: "second", size: "xl"}) }}
+If you choose to add links, buttons or other interactive elements in the green confirmation panel, they will not be accessible. You'll need to make changes to the panel or focus state style to make them accessible and meet a minimum contrast ratio of 3:1.
### Help users who bookmark the page
@@ -79,20 +45,6 @@ If you cannot, make sure your service responds in a helpful way when users retur
- starting a new application
- what to do or who to contact if they have a problem with their application
-
- {{ govukTag({
- text: "WCAG 2.2",
- classes: "app-tag"
- }) }}
-
Allow users to select and copy text within a confirmation page as well as its panel. For example, users should be able to select and copy a booking number. This relates to WCAG 2.2 success criterion 3.3.7 Redundant Entry.
-
-
-Consider offering an option for the user to copy information in the panel component area into their device’s clipboard if there’s information that the user is expected to:
-
-- save
-- remember
-- copy
-
## Research on this pattern
[Read a blog post about users who bookmark confirmation pages](https://designnotes.blog.gov.uk/2015/12/10/do-users-return-to-your-service-after-finishing/).
diff --git a/src/patterns/contact-a-department-or-service-team/index.md b/src/patterns/contact-a-department-or-service-team/index.md
index cfc7bd5c0a..aabe775e60 100644
--- a/src/patterns/contact-a-department-or-service-team/index.md
+++ b/src/patterns/contact-a-department-or-service-team/index.md
@@ -25,7 +25,7 @@ Give users contact information within your service.
To help users to 'Contact a department or service team' and meet the new WCAG 2.2 criteria, make sure that users can successfully:
-- [find contact details to get help in a consistent place on each page](/patterns/contact-a-department-or-service-team/#wcag-consistent-contact)
+- [find contact details in a consistent place across a set of pages](/patterns/contact-a-department-or-service-team/#wcag-consistent-contact)
See the full list of [components and patterns affected by WCAG 2.2](/accessibility/WCAG-2.2/#components-and-patterns-affected-in-the-design-system).
{% endset %}
@@ -58,8 +58,8 @@ Show contact channels in the same order throughout your service. This helps user
text: "WCAG 2.2",
classes: "app-tag"
}) }}
-
If you use this pattern across a set of pages, make sure to place the contact information consistently on each page.
-
For example, if you place a ‘contact us’ section at the end of one page within a set of pages, then you should place any ‘contact us’ sections on other pages within the set at the end of the other pages as well.
+
If you repeat a particular set of contact details on different pages, show them in the same place on each page.
+
For example, if you show a ‘contact us’ section at the end of one help page, any other help pages that include the same ‘contact us’ section should have them shown at the end of the page as well.
This is to comply with WCAG 2.2 success criterion 3.2.6 Consistent Help.
- {{ govukTag({
- text: "WCAG 2.2",
- classes: "app-tag"
- }) }}
-
Save cookie preferences for returning users whenever technically possible, so they do not need to enter their preferences again. This relates to WCAG 2.2 success criterion 3.3.7 Redundant Entry.
-
You must always write contact information in a clear and consistent way across ‘Page not found’ pages. This relates to WCAG 2.2 success criterion 3.2.6 Consistent Help.
+ You must always write contact information in a clear and consistent way across ‘Page not found’ and similar service error pages. This relates to WCAG 2.2 success criterion 3.2.6 Consistent Help.
Do not use:
diff --git a/src/patterns/problem-with-the-service-pages/index.md b/src/patterns/problem-with-the-service-pages/index.md
index 5c870fea4d..620ce89d8d 100644
--- a/src/patterns/problem-with-the-service-pages/index.md
+++ b/src/patterns/problem-with-the-service-pages/index.md
@@ -25,7 +25,7 @@ This guidance is for government teams that build online services. [To find infor
To use ‘There is a problem with the service pages' and meet the new Web Content Accessibility Guidelines (WCAG) 2.2 criteria, make sure that users can successfully:
-- [get contact information in a consistent way across 'There is a problem with the service pages' pages](/patterns/problem-with-the-service-pages/#wcag-consistent-content-problem-service)
+- [get contact information in a consistent way](/patterns/problem-with-the-service-pages/#wcag-consistent-content-problem-service)
- [resume the service using information they've previously entered, if possible](/patterns/problem-with-the-service-pages/#wcag-resume-previous-entered-information)
See the full list of [components and patterns affected by WCAG 2.2](/accessibility/WCAG-2.2/#components-and-patterns-affected-in-the-design-system).
@@ -98,7 +98,7 @@ You might choose to link to a ‘contact information’ page, such as one shown
text: "WCAG 2.2",
classes: "app-tag"
}) }}
- You must always write contact information in a clear and consistent way across ‘There is a problem with the service’ pages. This relates to WCAG 2.2 success criterion 3.2.6 Consistent Help.
+ You must always write contact information in a clear and consistent way across ‘There is a problem with the service’ and similar service error pages. This relates to WCAG 2.2 success criterion 3.2.6 Consistent Help.
### Service has a specific page that includes numbers and opening times
diff --git a/src/patterns/service-unavailable-pages/index.md b/src/patterns/service-unavailable-pages/index.md
index e2cb48b243..5fd362f853 100644
--- a/src/patterns/service-unavailable-pages/index.md
+++ b/src/patterns/service-unavailable-pages/index.md
@@ -25,7 +25,7 @@ This guidance is for government teams that build online services. [To find infor
To use ‘Service unavailable pages' and meet the new Web Content Accessibility Guidelines (WCAG) 2.2 criteria, make sure that users can successfully:
-- [get contact information in a consistent way across 'Service unavailable pages'](/patterns/service-unavailable-pages/#wcag-consistent-content-service-unavailable)
+- [get contact information in a consistent way](/patterns/service-unavailable-pages/#wcag-consistent-content-service-unavailable)
See the full list of [components and patterns affected by WCAG 2.2](/accessibility/WCAG-2.2/#components-and-patterns-affected-in-the-design-system).
{% endset %}
@@ -70,7 +70,7 @@ Contact information should either be:
text: "WCAG 2.2",
classes: "app-tag"
}) }}
- You must always write contact information in a clear and consistent way across ‘Service unavailable’ pages. This relates to WCAG 2.2 success criterion 3.2.6 Consistent Help.
+ You must always write contact information in a clear and consistent way across ‘Service unavailable’ and similar service error pages. This relates to WCAG 2.2 success criterion 3.2.6 Consistent Help.
Have clear and concise content and do not use: