From 8e0bcc84dc5643db3bb434a67c1e04030707a1d1 Mon Sep 17 00:00:00 2001 From: Tom Byers Date: Mon, 22 Feb 2021 13:43:22 +0000 Subject: [PATCH 01/11] Update accessibility statement with new issues We had an audit in February of this year but did not update the accessibility statement to reflect the issues identified as fixed or to include new issues it produced. Some of the dates for fixed have also not been updated for a long time. This adds those changes, with placeholders for dates assigned to each issue. This content is now ready for review. The dates will be assigned when that is complete. --- .../views/accessibility_statement.html | 53 ++++++++++++++++--- 1 file changed, 47 insertions(+), 6 deletions(-) diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html index 834f3a7bd..7ffca39b0 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -38,7 +38,14 @@ We know some parts of this website are not fully accessible:

@@ -80,7 +87,7 @@

- GOV.UK Notify is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below. + GOV.UK Notify is partially compliant with the Web Content Accessibility Guidelines (WCAG) version 2.1 AA standard, due to the non-compliances listed below.

Non-accessible content

@@ -92,11 +99,45 @@

Non compliance with the accessibility regulations

- 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. + The following content on the Notify website is not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard:

+ + +

Problems with using the interface

+ +

+ The following problems have been identified with the user interface: +

+ + +

PDFs and other documents

@@ -117,7 +158,7 @@

- We’ll continue to investigate the cause of this issue and, if possible, fix it by March 2021. + We’ll continue to investigate the cause of this issue and, if possible, fix it by [TODO date].

From c111a68b5764c5903612fc7b14814767c612c062 Mon Sep 17 00:00:00 2001 From: karlchillmaid Date: Wed, 11 Aug 2021 15:41:39 +0100 Subject: [PATCH 02/11] Update content --- app/templates/views/accessibility_statement.html | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html index 7ffca39b0..0d54e60b7 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -117,26 +117,26 @@

Problems with using the interface

- The following problems have been identified with the user interface: + We’ve identified the following problems with the user interface:

-
    +
    1. - The heading on pages for folders is announced as multiple sentences if it has parent folders when using the JAWS screen reader. We plan to fix this by [TODO date]. + The JAWS screen reader announces template folder page headings as multiple sentences. We plan to fix this by [TODO date].
    2. - The validation we use to help users recover from errors has problems which make it hard to know when errors occur and to understand them. We plan to fix this by [TODO date]. + Our validation errors cause problems for screen readers. This means it can be hard to know when an error has occurred or what to do next. We plan to fix this by [TODO date].
    3. The way we label the different regions of our pages is confusing for screen reader users. We plan to fix this by [TODO date].
    4. - The component used to select a time and date to send your messages has several problems which make it confusing to use with a screen reader. We plan to fix this by [TODO date]. + Choosing the date and time you want to send a message using a screen reader can be confusing. We plan to fix this by [TODO date].
    5. - The version of our checkboxes that can expand and collapse has several problems which make it confusint o use with a screen reader. + Expanding and collapsing groups of checkboxes using a screen reader can be confusing. We plan to fix this by [TODO date].
      6. -
+

PDFs and other documents From 2bb460fff25a377ada82dfd4aa4deabec0c61250 Mon Sep 17 00:00:00 2001 From: karlchillmaid Date: Wed, 11 Aug 2021 15:42:14 +0100 Subject: [PATCH 03/11] Update content --- app/templates/views/accessibility_statement.html | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html index 0d54e60b7..d05e1daaf 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -102,17 +102,17 @@ The following content on the Notify website is not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard:

- +

Problems with using the interface

From 6650e1663cdbbee71c03d0d666969eaa81fa0728 Mon Sep 17 00:00:00 2001 From: karlchillmaid Date: Wed, 11 Aug 2021 23:26:56 +0100 Subject: [PATCH 04/11] Update content --- app/templates/views/accessibility_statement.html | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html index d05e1daaf..706fb89a6 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -38,14 +38,14 @@ We know some parts of this website are not fully accessible:

    -
  • our button to upload CSV files is labelled in a way that is confusing for users of some assistive technologies
    • -
  • the heading on pages for folders is announced confusingly on some screen readers
    • -
  • our button that lets users copy some text to the clipboard doesn't work with some screen readers
    • -
  • our icons don't appear when using high contrast mode on Windows
    • -
  • the validation we use to help users recover from errors has several problems that make that harder for screen reader users
    • -
  • the way we label the different regions of our pages is confusing for screen reader users
    • -
  • our component that lets you select a time to send your messages is hard to use with screen readerss
    • -
  • our component that allows checkboxes to be in a region that can be collapsed is hard to use with screen readers
    • +
  • the ‘upload a file’ button may cause issues for some users
    • +
  • if a team adds template folders, screen readers may announce the page heading in a confusing way
    • +
  • the ‘copy to clipboard’ button does not work with some screen readers
    • +
  • Windows users cannot view our icons in high contrast mode
    • +
  • validation errors may be confusing for screen reader users
    • +
  • the way that screen readers announce the different regions of our pages can be confusing
    • +
  • choosing the date and time to send a message may be hard for some screen reader users
    • +
  • screen reader users may find it expand or collapse groups of checkboxes
  • one page links to a PDF document that is not fully accessible
  • the Notify status page has several accessibility issues
From c5f498f1e895f479d480094c49588172cbb42e58 Mon Sep 17 00:00:00 2001 From: karlchillmaid Date: Fri, 13 Aug 2021 11:51:24 +0100 Subject: [PATCH 05/11] Add dates and update WCAG acronym --- .../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 706fb89a6..36191949b 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -99,18 +99,18 @@

Non compliance with the accessibility regulations

- The following content on the Notify website is not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard: + The following content on the Notify website is not compliant with the WCAG version 2.1 AA standard:

  1. - The (before HTML) code for the ‘upload a file’ button may cause issues for assistive technology users. This fails success criterion 1.3.1: info and relationships. We plan to fix this by [TODO date]. + The (before HTML) code for the ‘upload a file’ button may cause issues for assistive technology users. This fails success criterion 1.3.1: info and relationships. We plan to fix this by the end of October 2021.
  2. - The JAWS and NVDA screen readers do not announce the ‘copy text to clipboard’ component. This fails success criterion 4.1.3: status messages. We plan to fix this by [TODO date]. + The JAWS and NVDA screen readers do not announce the ‘copy to clipboard’ button. This fails success criterion 4.1.3: status messages. We plan to fix this by the end of October 2021.
  3. - Some icons do not appear when using high contrast mode on Windows. This fails success criterion 1.4.8: visual presentation. We plan to fix this by [TODO date]. + Some icons do not appear when using high contrast mode on Windows. This fails success criterion 1.4.8: visual presentation. We plan to fix this by the end of October 2021.
@@ -122,19 +122,19 @@
  1. - The JAWS screen reader announces template folder page headings as multiple sentences. We plan to fix this by [TODO date]. + The JAWS screen reader announces template folder page headings as multiple sentences. We hope to be able to fix this by the end of 2021.
  2. - Our validation errors cause problems for screen readers. This means it can be hard to know when an error has occurred or what to do next. We plan to fix this by [TODO date]. + Our validation errors cause problems for screen readers. This means it can be hard to know when an error has occurred or what to do next. We hope to be able to fix this by the end of 2021.
  3. - The way we label the different regions of our pages is confusing for screen reader users. We plan to fix this by [TODO date]. + The way we label the different regions of our pages is confusing for screen reader users. We plan to fix this by the end of October 2021.
  4. - Choosing the date and time you want to send a message using a screen reader can be confusing. We plan to fix this by [TODO date]. + Choosing the date and time you want to send a message using a screen reader can be confusing. We hope to be able to fix this by the end of 2021.
  5. - Expanding and collapsing groups of checkboxes using a screen reader can be confusing. We plan to fix this by [TODO date]. + Expanding and collapsing groups of checkboxes using a screen reader can be confusing. We hope to be able to fix this by the end of 2021.
@@ -158,7 +158,7 @@

- We’ll continue to investigate the cause of this issue and, if possible, fix it by [TODO date]. + We’ll continue to investigate the cause of this issue and, if possible, fix it by the end of 2021.

From be0cc955bd7f79f96329b4f35f031ca42b2fd439 Mon Sep 17 00:00:00 2001 From: karlchillmaid Date: Fri, 13 Aug 2021 11:59:52 +0100 Subject: [PATCH 06/11] Update commitment dates --- app/templates/views/accessibility_statement.html | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html index 36191949b..56cb63949 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -122,19 +122,19 @@
  1. - The JAWS screen reader announces template folder page headings as multiple sentences. We hope to be able to fix this by the end of 2021. + The JAWS screen reader announces template folder page headings as multiple sentences. We hope to fix this by the end of 2021.
  2. - Our validation errors cause problems for screen readers. This means it can be hard to know when an error has occurred or what to do next. We hope to be able to fix this by the end of 2021. + Our validation errors cause problems for screen readers. This means it can be hard to know when an error has occurred or what to do next. We hope to fix this by the end of 2021.
  3. - The way we label the different regions of our pages is confusing for screen reader users. We plan to fix this by the end of October 2021. + The way we label the different regions of our pages is confusing for screen reader users. We expect to fix this by the end of October 2021.
  4. - Choosing the date and time you want to send a message using a screen reader can be confusing. We hope to be able to fix this by the end of 2021. + Choosing the date and time you want to send a message using a screen reader can be confusing. We hope to fix this by the end of 2021.
  5. - Expanding and collapsing groups of checkboxes using a screen reader can be confusing. We hope to be able to fix this by the end of 2021. + Expanding and collapsing groups of checkboxes using a screen reader can be confusing. We hope to fix this by the end of 2021.
From ab132bab2aac1a883775b9b6db39a08a2fbddcbf Mon Sep 17 00:00:00 2001 From: karlchillmaid Date: Fri, 13 Aug 2021 12:00:03 +0100 Subject: [PATCH 07/11] Update commitment dates --- app/templates/views/accessibility_statement.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html index 56cb63949..85c13304d 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -104,13 +104,13 @@
  1. - The (before HTML) code for the ‘upload a file’ button may cause issues for assistive technology users. This fails success criterion 1.3.1: info and relationships. We plan to fix this by the end of October 2021. + The (before HTML) code for the ‘upload a file’ button may cause issues for assistive technology users. This fails success criterion 1.3.1: info and relationships. We expect to fix this by the end of October 2021.
  2. - The JAWS and NVDA screen readers do not announce the ‘copy to clipboard’ button. This fails success criterion 4.1.3: status messages. We plan to fix this by the end of October 2021. + The JAWS and NVDA screen readers do not announce the ‘copy to clipboard’ button. This fails success criterion 4.1.3: status messages. We expect to fix this by the end of October 2021.
  3. - Some icons do not appear when using high contrast mode on Windows. This fails success criterion 1.4.8: visual presentation. We plan to fix this by the end of October 2021. + Some icons do not appear when using high contrast mode on Windows. This fails success criterion 1.4.8: visual presentation. We expect to fix this by the end of October 2021.
From 18312cfdaa83ffee5d79006d4187ee81442fff41 Mon Sep 17 00:00:00 2001 From: karlchillmaid Date: Fri, 13 Aug 2021 12:06:18 +0100 Subject: [PATCH 08/11] Update success criterion and review date --- .../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 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:

@@ -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 %} From 1fa2d6fc581ba347578863772e8e20ce41d7d0b3 Mon Sep 17 00:00:00 2001 From: karlchillmaid Date: Fri, 13 Aug 2021 12:12:51 +0100 Subject: [PATCH 09/11] Update last tested date --- 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 00e8c488d..a0404d744 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -190,7 +190,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 DAC. + The parts of the website used to send text messages, emails and letters were last tested in February 2021. 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 342e0e9d0547b73e90b3901738ce936147fb2a00 Mon Sep 17 00:00:00 2001 From: karlchillmaid Date: Fri, 13 Aug 2021 14:36:02 +0100 Subject: [PATCH 10/11] Update bullet formatting and content --- .../views/accessibility_statement.html | 32 ++++++++++++------- 1 file changed, 20 insertions(+), 12 deletions(-) diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html index a0404d744..a34773940 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -102,17 +102,21 @@ The following content on the Notify website is not compliant with the WCAG version 2.1 AA standard:

-
    +
+ + +

+ We expect to fix these issues by the end of October 2021. +

Problems with using the interface

@@ -120,23 +124,27 @@ We’ve identified the following problems with the user interface:

-
    +
    • - The JAWS screen reader announces template folder page headings as multiple sentences. We hope to fix this by the end of 2021. + the JAWS screen reader announces template folder page headings as multiple sentences
    • - Our validation errors cause problems for screen readers. This means it can be hard to know when an error has occurred or what to do next. We hope to fix this by the end of 2021. + our validation errors cause problems for screen readers - this means it can be hard to know when an error has occurred or what to do next
    • - The way we label the different regions of our pages is confusing for screen reader users. We expect to fix this by the end of October 2021. + the way we label the different regions of our pages is confusing for screen reader users
    • - Choosing the date and time you want to send a message using a screen reader can be confusing. We hope to fix this by the end of 2021. + choosing the date and time you want to send a message using a screen reader can be confusing
    • - Expanding and collapsing groups of checkboxes using a screen reader can be confusing. We hope to fix this by the end of 2021. + expanding and collapsing groups of checkboxes using a screen reader can be confusing
      • -
+ + +

+ We hope to fix these issues by the end of December 2021. +

PDFs and other documents From 7b49dbb236f50b64c9d8d7ec623d2e79d6b13f12 Mon Sep 17 00:00:00 2001 From: karlchillmaid Date: Fri, 13 Aug 2021 14:41:11 +0100 Subject: [PATCH 11/11] Fix link markup --- .../views/accessibility_statement.html | 38 +++++++++---------- 1 file changed, 19 insertions(+), 19 deletions(-) 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:

- +