diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html
index 85c13304d..00e8c488d 100644
--- a/app/templates/views/accessibility_statement.html
+++ b/app/templates/views/accessibility_statement.html
@@ -166,19 +166,19 @@
- The following content on the Notify status page is not compliant with the Web Content Accessibility Guidelines 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 WCAG 2.1 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 WCAG 2.1 success criterion 1.3.1 (Info and Relationships)
- - our status page ‘subscribe to updates’ link does not contain programmatically discernible link text – this fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships)
- - our status page subscribe to updates form fields do not contain an explicit label – this fails WCAG 2.1 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 WCAG 2.1 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 WCAG 2.1A 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 WCAG 2.1 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 WCAG 2.1 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
@@ -198,6 +198,6 @@
- This statement was prepared on 23 September 2020. It was last reviewed on 14 January 2021.
+ This statement was prepared on 23 September 2020. It was last reviewed on 13 August 2021.
{% endblock %}