From 181b45c3192121bbd98ffce2b5ea6d1f4bae3161 Mon Sep 17 00:00:00 2001 From: Tom Byers Date: Thu, 14 Jan 2021 10:17:47 +0000 Subject: [PATCH 1/3] Update issue with moving templates/folders --- app/templates/views/accessibility_statement.html | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html index 0aeed96c6..047aa4761 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -92,7 +92,9 @@

Non compliance with the accessibility regulations

- Screen reader users may find the process of moving templates and folders confusing. This fails WCAG 4.1.2 success criteria (Name, role, value). We plan to fix this by November 2020. + Screen reader users may find the process of moving templates and folders confusing. This fails WCAG 4.1.2 success criteria (Name, role, value).

+ +

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.

@@ -147,7 +149,7 @@

- The parts of the website used to send text messages, emails and letters were last tested on 15 July 2020. The emails we send out, the web pages users see when they are sent a file by Notify and a sample letter PDF were last tested on 11th March 2019. Both tests were carried out by the Digital Accessibility Centre (DAC). + The parts of the website used to send text messages, emails and letters were last tested on 15 July 2020. The emails we send out, the web pages users see when they are sent a file by Notify and a sample letter PDF were last tested on 11th March 2019. Both tests were carried out by DAC.

From 900c2b9f8c43d8e9b031fa4c89081ab81fcb443b Mon Sep 17 00:00:00 2001 From: Tom Byers Date: Thu, 14 Jan 2021 11:55:50 +0000 Subject: [PATCH 2/3] 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 @@

Non compliance with the accessibility regulations

- Screen reader users may find the process of moving templates and folders confusing. This fails WCAG 4.1.2 success criteria (Name, role, value).

+ Screen reader users may find the process of moving templates and folders confusing. This fails WCAG 2.1 success criteria 4.1.2 (Name, role, value).

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.

@@ -129,15 +129,15 @@

@@ -157,6 +157,6 @@

- 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.

{% endblock %} From a6e4022ce73b651a1ae1c16af4ff8b86f9c359ef Mon Sep 17 00:00:00 2001 From: Tom Byers Date: Thu, 14 Jan 2021 14:03:57 +0000 Subject: [PATCH 3/3] Fix typo in status page issue Co-authored-by: karlchillmaid --- app/templates/views/accessibility_statement.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html index ffd4b8588..834f3a7bd 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -132,7 +132,7 @@
  • an incorrect heading hierarchy which fails WCAG 2.1 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’ 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)