diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html
index a34773940..10a4bb9ae 100644
--- a/app/templates/views/accessibility_statement.html
+++ b/app/templates/views/accessibility_statement.html
@@ -10,7 +10,7 @@
Accessibility statement
- This accessibility statement applies to the www.notifications.service.gov.uk domain. It does not apply to the GOV.UK Notify API documentation subdomain.
+ This accessibility statement applies to the www.notifications.service.gov.uk domain. It does not apply to the GOV.UK Notify API documentation subdomain.
@@ -29,7 +29,7 @@
- AbilityNet has advice on making your device easier to use if you have a disability.
+ AbilityNet has advice on making your device easier to use if you have a disability.
How accessible this website is
@@ -53,11 +53,11 @@
We also know that the emails Notify sends are not fully accessible. The JAWS and NVDA screen readers announce extra spaces in emails when you view them in Microsoft Outlook.
-
+
Feedback and contact information
- If you need any part of this service in a different format like large print, audio recording or braille, contact the GOV.UK Notify team.
+ If you need any part of this service in a different format like large print, audio recording or braille, contact the GOV.UK Notify team.
@@ -67,7 +67,7 @@
Reporting accessibility problems with this website
- We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact the GOV.UK Notify team.
+ We’re always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact the GOV.UK Notify team.
Enforcement procedure
@@ -77,7 +77,7 @@
- Find out how to contact the GOV.UK Notify team.
+ Find out how to contact the GOV.UK Notify team.
Technical information about this website’s accessibility
@@ -104,13 +104,13 @@
@@ -174,19 +174,19 @@
- The following content on the Notify status page is not compliant with the WCAG version 2.1 AA standard:
+ The following content on the Notify status page is not compliant with the WCAG version 2.1 AA standard:
-
+
- - an incorrect heading hierarchy which fails success criterion 1.3.1: info and relationships
+ - an incorrect heading hierarchy which fails success criterion 1.3.1: info and relationships
- missing level 1 headings (users may not be able to accurately determine the structure of content on the page)
- - our status incident page is missing the main heading and the status home page has an incorrect heading hierarchy – this fails success criterion 1.3.1: info and relationships
- - our status page ‘subscribe to updates’ link does not contain programmatically discernible link text – this fails success criterion 1.3.1: info and relationships
- - our status page subscribe to updates form fields do not contain an explicit label – this fails success criterion 1.3.1: info and relationships
- - our status page subscribe to updates forms do not indicate to users that they are expandable or collapsible – this fails success criterion 4.1.2: name, role, value
- - our status page subscribe to updates forms contain some text that does not meet the minimum colour contrast requirements – this fails success criterion 1.4.3: contrast, minimum
- - our status page subscribe to updates form close link (x) is not descriptive enough for some users to determine its function or purpose – this fails success criterion 2.4.4: link purpose, in context
- - our status page subscribe to updates forms, when submitted with incorrect data, do not inform screen reader users of the error message when it becomes available – this fails success criterion 4.1.3: status messages
+ - our status incident page is missing the main heading and the status home page has an incorrect heading hierarchy – this fails success criterion 1.3.1: info and relationships
+ - our status page ‘subscribe to updates’ link does not contain programmatically discernible link text – this fails success criterion 1.3.1: info and relationships
+ - our status page subscribe to updates form fields do not contain an explicit label – this fails success criterion 1.3.1: info and relationships
+ - our status page subscribe to updates forms do not indicate to users that they are expandable or collapsible – this fails success criterion 4.1.2: name, role, value
+ - our status page subscribe to updates forms contain some text that does not meet the minimum colour contrast requirements – this fails success criterion 1.4.3: contrast, minimum
+ - our status page subscribe to updates form close link (x) is not descriptive enough for some users to determine its function or purpose – this fails success criterion 2.4.4: link purpose, in context
+ - our status page subscribe to updates forms, when submitted with incorrect data, do not inform screen reader users of the error message when it becomes available – this fails success criterion 4.1.3: status messages