From 900c2b9f8c43d8e9b031fa4c89081ab81fcb443b Mon Sep 17 00:00:00 2001
From: Tom Byers <tombaromba@gmail.com>
Date: Thu, 14 Jan 2021 11:55:50 +0000
Subject: [PATCH] Bump updated date to be today

---
 .../views/accessibility_statement.html        | 20 +++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html
index 047aa4761..ffd4b8588 100644
--- a/app/templates/views/accessibility_statement.html
+++ b/app/templates/views/accessibility_statement.html
@@ -92,7 +92,7 @@
   <h3 class="heading-small">Non compliance with the accessibility regulations</h3>
 
   <p class="govuk-body">
-    Screen reader users may find the process of moving templates and folders confusing. This fails <a class="govuk-link" href="https://www.w3.org/TR/WCAG21/#name-role-value">WCAG 4.1.2 success criteria (Name, role, value)</a>.</p>
+    Screen reader users may find the process of moving templates and folders confusing. This fails <a class="govuk-link" href="https://www.w3.org/TR/WCAG21/#name-role-value">WCAG 2.1 success criteria 4.1.2 (Name, role, value)</a>.</p>
 
   <p class="govuk-body">We made some changes that will be tested by the Digital Accessibility Centre (DAC) at the end of January. If possible, we plan to fix this by March 2021.
   </p>
@@ -129,15 +129,15 @@
   </p>
     
   <ul class="govuk-list govuk-list--bullet">
-    <li>an incorrect heading hierarchy which fails WCAG 2.1A 1.3.1 success criterion (Info and Relationships)</li>
+    <li>an incorrect heading hierarchy which fails <a href="https://www.w3.org/TR/WCAG21/#info-and-relationships">WCAG 2.1 success criterion 1.3.1 (Info and Relationships)</a></li>
     <li>missing level 1 headings (users may not be able to accurately determine the structure of content on the page)</li>
-    <li>our status incident page is missing the main heading and the status home page has an incorrect heading hierarchy – this fails WCAG 2.1A 1.3.1 success criterion (Info and Relationships)</li>
-    <li>our status page ‘subscribe to updates’ link does not contain programmatically discernible link text – This fails WCAG 2.1A 1.3.1 success criterion (Info and Relationships)</li>
-    <li>our status page subscribe to updates form fields do not contain an explicit label – this fails WCAG 2.1A 1.3.1 success criterion (Info and Relationships)</li>
-    <li>our status page subscribe to updates forms do not indicate to users that they are expandable or collapsible – this fails WCAG 2.1A 4.1.2 success criterion (Name, Role, Value)</li>
-    <li>our status page subscribe to updates forms contain some text that does not meet the minimum colour contrast requirements – this fails WCAG 2.1AA 1.4.3 success criterion (Contrast, Minimum)</li>
-    <li>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.1A 2.4.4 success criterion (Link Purpose, In Context)</li>
-    <li>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.1AA 4.1.3 success criterion (Status Messages)</li>
+    <li>our status incident page is missing the main heading and the status home page has an incorrect heading hierarchy – this fails <a href="https://www.w3.org/TR/WCAG21/#info-and-relationships">WCAG 2.1 success criterion 1.3.1 (Info and Relationships)</a></li>
+    <li>our status page ‘subscribe to updates’ link does not contain programmatically discernible link text – This fails <a href="https://www.w3.org/TR/WCAG21/#info-and-relationships">WCAG 2.1 success criterion 1.3.1 (Info and Relationships)</a></li>
+    <li>our status page subscribe to updates form fields do not contain an explicit label – this fails <a href="https://www.w3.org/TR/WCAG21/#info-and-relationships">WCAG 2.1 success criterion 1.3.1 (Info and Relationships)</a></li>
+    <li>our status page subscribe to updates forms do not indicate to users that they are expandable or collapsible – this fails <a href="https://www.w3.org/TR/WCAG21/#name-role-value">WCAG 2.1 success criterion 4.1.2 (Name, Role, Value)</a></li>
+    <li>our status page subscribe to updates forms contain some text that does not meet the minimum colour contrast requirements – this fails <a href="https://www.w3.org/TR/WCAG21/#contrast-minimum">WCAG 2.1A success criterion 1.4.3 (Contrast, Minimum)</a></li>
+    <li>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 <a href="https://www.w3.org/TR/WCAG21/#link-purpose-in-context">WCAG 2.1 success criterion 2.4.4 (Link Purpose, In Context)</a></li>
+    <li>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 <a href="https://www.w3.org/TR/WCAG21/#status-messages">WCAG 2.1 success criterion 4.1.3 (Status Messages)</a></li>
   </ul>
 
   <p class="govuk-body">
@@ -157,6 +157,6 @@
   </p>
 
   <p class="govuk-body">
-    This statement was prepared on 23 September 2020. It was last reviewed on 19 November 2020.
+    This statement was prepared on 23 September 2020. It was last reviewed on 14 January 2021.
   </p>
 {% endblock %}