From 5241ea3ef0b1c9ff4052c5ab777472465ed293ce Mon Sep 17 00:00:00 2001 From: Tom Byers Date: Fri, 18 Sep 2020 14:40:47 +0100 Subject: [PATCH 01/14] Add basic page for accessibility statement --- app/main/views/index.py | 5 ++++ app/templates/admin_template.html | 4 +++ .../views/accessibility_statement.html | 29 +++++++++++++++++++ 3 files changed, 38 insertions(+) create mode 100644 app/templates/views/accessibility_statement.html diff --git a/app/main/views/index.py b/app/main/views/index.py index 7e59a0347..2bca8b6cc 100644 --- a/app/main/views/index.py +++ b/app/main/views/index.py @@ -53,6 +53,11 @@ def privacy(): return render_template('views/privacy.html') +@main.route('/accessibility-statement') +def accessibility_statement(): + return render_template('views/accessibility_statement.html') + + @main.route('/pricing') def pricing(): return render_template( diff --git a/app/templates/admin_template.html b/app/templates/admin_template.html index 73e46b977..4d5f1c006 100644 --- a/app/templates/admin_template.html +++ b/app/templates/admin_template.html @@ -140,6 +140,10 @@ { "href": url_for("main.cookies"), "text": "Cookies" + }, + { + "href": url_for("main.accessibility_statement"), + "text": "Accessibility statement" } ] %} diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html new file mode 100644 index 000000000..a03a46e25 --- /dev/null +++ b/app/templates/views/accessibility_statement.html @@ -0,0 +1,29 @@ +{% extends "content_template.html" %} +{% from "components/service-link.html" import service_link %} + +{% block per_page_title %} + Accessibility statement +{% endblock %} + +{% block content_column_content %} + +

Accessibility statement

+ +

+ This accessibility statement applies to content published on the www.notifications.service.gov.uk domain. It does not apply to the GOV.UK Notify API documentation subdomain: https://docs.notifications.service.gov.uk. +

+ +

How accessible this website is

+ +

Feedback and contact information

+ +

Reporting accessibility problems with this website

+ +

Enforcement procedure

+ +

Technical information about this website’s accessibility

+ +

Compliance status

+ +{% endblock %} + From 0e0f5dcc5d3956ca22ca5c746193a9018c1b755f Mon Sep 17 00:00:00 2001 From: Tom Byers Date: Tue, 22 Sep 2020 16:18:00 +0100 Subject: [PATCH 02/14] Add copy from the draft document --- .../views/accessibility_statement.html | 143 +++++++++++++++++- 1 file changed, 142 insertions(+), 1 deletion(-) diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html index a03a46e25..7554111c8 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -13,17 +13,158 @@ This accessibility statement applies to content published on the www.notifications.service.gov.uk domain. It does not apply to the GOV.UK Notify API documentation subdomain: https://docs.notifications.service.gov.uk.

+

+ This website is run by the GOV.UK Notify team at the Government Digital Service (GDS). It is designed to be used by as many people as possible. You should be able to: +

+ + +

+ The text should be clear and simple to understand. +

+ +

+ AbilityNet has advice on making your device easier to use if you have a disability. +

+

How accessible this website is

+

+ We know some parts of this website are not fully accessible: +

+ + +

+ We know that the emails Notify sends are not fully accessible: +

+ +

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

+ +

+ We’ll consider your request and get back to you within one working day. +

+

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: [provide both details of how to report these issues to your organisation, and contact details for the unit or person responsible for dealing with these reports]. +

+

Enforcement procedure

+

+ The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS). +

+ +

+ Find out how to contact the GOV.UK Notify team. +

+

Technical information about this website’s accessibility

-

Compliance status

+

+ GDS is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. +

+

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

+ +

Non-accessible content

+ +

+ The content listed below is non-accessible for the following reasons. +

+ +

Non compliance with the accessibility regulations

+ +

+ Low vision users cannot access the table we use to show CSV data when viewed at high zoom. This fails WCAG 1.4.10 success criteria (Reflow). +

+ +

+ Keyboard-only and voice activation users cannot focus on the table we use to show CSV data. This fails WCAG 2.1.1 success criteria (Keyboard). +

+ +

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

+ +

+ Screenreader users may find it confusing that a specific part of some pages is focused when they load. This fails WCAG 2.4.3 success criteria (Focus Order) +

+ +

+ PDFs and other documents +

+ +

+ Some pages have links to PDF documents, and these PDF documents are not fully accessible. This is not a fail under any WCAG 2.1 success criterion. We provide the information contained in these PDFs in an accessible HTML format. +

+ +

+ Some of our PDFs are essential to providing our services. For example, we have a PDF that shows the layout of our letter specification. We provide a written description of this information on an HTML page as an accessible alternative. +

+ +

+ The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. For example, we do not plan to fix [example of non-essential document]. +

+ +

+ Any new PDFs or Word documents we publish will meet accessibility standards. +

+ +

+ Emails +

+ +

+ NVDA screen reader announces the URL of the GOV.UK logo image in emails when you view them in Microsoft Outlook +

+ +

+ JAWS and NVDA screen readers announce extra spaces in emails when you view them in Microsoft Outlook +

+ +

+ The Voiceover screen reader announces the hidden summary sentence in our emails when you open them in Apple Mail +

+ +

+ How we tested this service +

+ +

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

+ +

+ We decided which pages to test based on the most common tasks that GOV.UK Notify users need to complete. We also tested a sample of pages with common user interface components. +

+ +

+ This statement was prepared on 22 September 2020. It was last reviewed on 22 September 2020. +

{% endblock %} From 300af7126e0a0bc7718da8363f8f5fa6cef8bbdf Mon Sep 17 00:00:00 2001 From: Tom Byers Date: Tue, 22 Sep 2020 16:53:33 +0100 Subject: [PATCH 03/14] Updates to issues in various places --- .../views/accessibility_statement.html | 17 ++++++----------- 1 file changed, 6 insertions(+), 11 deletions(-) diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html index 7554111c8..0d1531b53 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -52,7 +52,6 @@
  • NVDA screen reader announces the URL of the GOV.UK logo image in emails when you view them in Microsoft Outlook
  • JAWS and NVDA screen readers announce extra spaces in emails when you view them in Microsoft Outlook
    • -
  • the Voiceover screen reader announces the hidden summary sentence in our emails when you open them in Apple Mail

Feedback and contact information

@@ -100,19 +99,19 @@

Non compliance with the accessibility regulations

- Low vision users cannot access the table we use to show CSV data when viewed at high zoom. This fails WCAG 1.4.10 success criteria (Reflow). + Low vision users cannot access the table we use to show CSV data when viewed at high zoom. This fails WCAG 1.4.10 success criteria (Reflow). We plan to fix this by the end of 2020.

- Keyboard-only and voice activation users cannot focus on the table we use to show CSV data. This fails WCAG 2.1.1 success criteria (Keyboard). + Keyboard-only and voice activation users cannot focus on the table we use to show CSV data. This fails WCAG 2.1.1 success criteria (Keyboard). 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). + 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.

- Screenreader users may find it confusing that a specific part of some pages is focused when they load. This fails WCAG 2.4.3 success criteria (Focus Order) + Screenreader users may find it confusing that a specific part of some pages is focused when they load. This fails WCAG 2.4.3 success criteria (Focus Order). We plan to fix this by October 2020.

@@ -140,15 +139,11 @@

- NVDA screen reader announces the URL of the GOV.UK logo image in emails when you view them in Microsoft Outlook + The NVDA screen reader announces the URL of the GOV.UK logo image in emails when viewed in Microsoft Outlook. This has been raised as an issue on NVDA's issue tracker.

- JAWS and NVDA screen readers announce extra spaces in emails when you view them in Microsoft Outlook -

- -

- The Voiceover screen reader announces the hidden summary sentence in our emails when you open them in Apple Mail + The JAWS and NVDA screen readers announce extra spaces in emails when viewed in Microsoft Outlook.

From 8343de1f26ae797c23c7c977be479a39e32a533d Mon Sep 17 00:00:00 2001 From: karlchillmaid Date: Tue, 22 Sep 2020 17:12:08 +0100 Subject: [PATCH 04/14] Update introduction content --- 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 0d1531b53..79bde0626 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 content published on the www.notifications.service.gov.uk domain. It does not apply to the GOV.UK Notify API documentation subdomain: https://docs.notifications.service.gov.uk. + This accessibility statement applies to the www.notifications.service.gov.uk domain. It does not apply to the GOV.UK Notify API documentation subdomain.

From bd592ff67b53086ee5994b7775822d68febafd79 Mon Sep 17 00:00:00 2001 From: karlchillmaid Date: Tue, 22 Sep 2020 19:14:09 +0100 Subject: [PATCH 05/14] Add status page information --- .../views/accessibility_statement.html | 49 ++++++++++++++----- 1 file changed, 36 insertions(+), 13 deletions(-) diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html index 79bde0626..2f9270307 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -42,7 +42,7 @@

  • keyboard-only and voice activation users cannot focus on the table we use to show CSV data
  • screen reader users may find the process of moving templates and folders confusing
  • some pages have links to PDF documents, and these PDFs are not fully accessible
    • -
  • Screenreader users may find it confusing that a specific part of some pages is focused when they load.
    • +
  • screen readers users may be disorientated when pages load with the focus on a specific area
  • Status page thing
    • @@ -111,7 +111,11 @@

    - Screenreader users may find it confusing that a specific part of some pages is focused when they load. This fails WCAG 2.4.3 success criteria (Focus Order). We plan to fix this by October 2020. + Screen reader users may find it confusing that a specific part of some pages is focused when they load. This fails WCAG 2.4.3 success criteria (Focus Order). We plan to fix this by October 2020. +

    + +

    + We plan to address these issues by March 2021.

    @@ -119,19 +123,10 @@

    - Some pages have links to PDF documents, and these PDF documents are not fully accessible. This is not a fail under any WCAG 2.1 success criterion. We provide the information contained in these PDFs in an accessible HTML format. -

    + Some pages have links to PDF documents, and these PDF documents are not fully accessible. This is not a fail under any WCAG 2.1 success criterion.

    - Some of our PDFs are essential to providing our services. For example, we have a PDF that shows the layout of our letter specification. We provide a written description of this information on an HTML page as an accessible alternative. -

    - -

    - The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. For example, we do not plan to fix [example of non-essential document]. -

    - -

    - Any new PDFs or Word documents we publish will meet accessibility standards. + For example, we have a PDF that shows the layout of our letter specification. We provide a written description of this information on an HTML page as an accessible alternative.

    @@ -146,6 +141,34 @@ The JAWS and NVDA screen readers announce extra spaces in emails when viewed in Microsoft Outlook.

    +

    + We plan to work with screen reader and email client suppliers to fix the email issues in 2021. +

    + +

    + Status page +

    + +

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

    + +
      +
    • an incorrect heading hierarchy which fails WCAG 2.1A 1.3.1 success criterion (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.1A 1.3.1 success criterion (Info and Relationships)
      • +
    • our status page ‘subscribe to updates’ link does not contain programmatically discernible link text – tThis fails WCAG 2.1A 1.3.1 success criterion (Info and Relationships)
      • +
    • 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)
      • +
    • 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)
      • +
    • 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)
      • +
    • 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)
      • +
    • 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)
      • +
    + +

    + We plan to have the status page issues addressed by the current supplier or move to an alternative supplier in 2021. +

    +

    How we tested this service

    From 6cfc62216e453f7c1cac3034f81aa7e63e0bea88 Mon Sep 17 00:00:00 2001 From: karlchillmaid Date: Tue, 22 Sep 2020 19:15:13 +0100 Subject: [PATCH 06/14] Update summary --- 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 2f9270307..87bf3016e 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -43,7 +43,7 @@
  • screen reader users may find the process of moving templates and folders confusing
  • some pages have links to PDF documents, and these PDFs are not fully accessible
  • screen readers users may be disorientated when pages load with the focus on a specific area
    • -
  • Status page thing
    • +
  • the Notify status page has several accessibility issues

    • From cd61479a4f0255c91dbf1686e4c4f653b329a2b2 Mon Sep 17 00:00:00 2001 From: karlchillmaid Date: Tue, 22 Sep 2020 20:47:05 +0100 Subject: [PATCH 07/14] Update PDF information --- 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 87bf3016e..120cdddfe 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -41,7 +41,7 @@

  • low vision users cannot access the table we use to show CSV data when viewed at high zoom
  • keyboard-only and voice activation users cannot focus on the table we use to show CSV data
  • screen reader users may find the process of moving templates and folders confusing
    • -
  • some pages have links to PDF documents, and these PDFs are not fully accessible
    • +
  • one page links to a PDF document that is not fully accessible
  • screen readers users may be disorientated when pages load with the focus on a specific area
  • the Notify status page has several accessibility issues
    • @@ -123,10 +123,10 @@

    - Some pages have links to PDF documents, and these PDF documents are not fully accessible. This is not a fail under any WCAG 2.1 success criterion.

    + One page links to a PDF documents that is not fully accessible. This is not a fail under any WCAG 2.1 success criterion.

    - For example, we have a PDF that shows the layout of our letter specification. We provide a written description of this information on an HTML page as an accessible alternative. + We provide a written description of the information in the PDF on an HTML page as an accessible alternative.

    From 2212d3a5e09b36e6ad242e7233c363e77ed79290 Mon Sep 17 00:00:00 2001 From: Tom Byers Date: Tue, 22 Sep 2020 20:56:38 +0100 Subject: [PATCH 08/14] Tweaks to issues summary & list + reporting --- app/templates/views/accessibility_statement.html | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html index 120cdddfe..58bd2b64b 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -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: [provide both details of how to report these issues to your organisation, and contact details for the unit or person responsible for dealing with these reports]. + 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

    @@ -114,10 +114,6 @@ Screen reader users may find it confusing that a specific part of some pages is focused when they load. This fails WCAG 2.4.3 success criteria (Focus Order). We plan to fix this by October 2020.

    -

    - We plan to address these issues by March 2021. -

    -

    PDFs and other documents

    From 2ec053ca3dfe79c8b724231d3e9b18e1041f8264 Mon Sep 17 00:00:00 2001 From: Tom Byers Date: Tue, 22 Sep 2020 21:45:13 +0100 Subject: [PATCH 09/14] Tweaks to email issue descriptions --- app/templates/views/accessibility_statement.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html index 58bd2b64b..ae0a629e2 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -130,7 +130,7 @@

    - The NVDA screen reader announces the URL of the GOV.UK logo image in emails when viewed in Microsoft Outlook. This has been raised as an issue on NVDA's issue tracker. + The NVDA screen reader announces the URL of the GOV.UK logo image in emails when viewed in Microsoft Outlook. This has been raised as an issue on NVDA’s issue tracker.

    @@ -138,7 +138,7 @@

    - We plan to work with screen reader and email client suppliers to fix the email issues in 2021. + We’ll continue to investigate the cause of these issues and, if possible, fix them by March 2021.

    From 798c6ebc48cd8f743929f2c37a3ce66ad55c15f8 Mon Sep 17 00:00:00 2001 From: Tom Byers Date: Wed, 23 Sep 2020 09:53:12 +0100 Subject: [PATCH 10/14] Exclude new page from navigation --- app/navigation.py | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/app/navigation.py b/app/navigation.py index 98edb97d9..5d1251917 100644 --- a/app/navigation.py +++ b/app/navigation.py @@ -127,6 +127,7 @@ class HeaderNavigation(Navigation): exclude = { 'accept_invite', 'accept_org_invite', + 'accessibility_statement', 'action_blocked', 'add_data_retention', 'add_organisation', @@ -518,6 +519,7 @@ class MainNavigation(Navigation): exclude = { 'accept_invite', 'accept_org_invite', + 'accessibility_statement', 'add_data_retention', 'add_organisation', 'add_service', @@ -743,6 +745,7 @@ class CaseworkNavigation(Navigation): exclude = { 'accept_invite', 'accept_org_invite', + 'accessibility_statement', 'action_blocked', 'add_data_retention', 'add_organisation', @@ -1067,6 +1070,7 @@ class OrgNavigation(Navigation): exclude = { 'accept_invite', 'accept_org_invite', + 'accessibility_statement', 'action_blocked', 'add_data_retention', 'add_organisation', From eba78ebf89fd263fc67904c765bcaf2069fc57f5 Mon Sep 17 00:00:00 2001 From: Tom Byers Date: Wed, 23 Sep 2020 11:09:06 +0100 Subject: [PATCH 11/14] Update preparation and review dates --- 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 ae0a629e2..421fca33f 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -178,7 +178,7 @@

    - This statement was prepared on 22 September 2020. It was last reviewed on 22 September 2020. + This statement was prepared on 23 September 2020. It was last reviewed on 23 September 2020.

    {% endblock %} From 5e18988a3b66bc2c72bffbe008ad0382426c0b78 Mon Sep 17 00:00:00 2001 From: Tom Byers Date: Wed, 23 Sep 2020 11:10:37 +0100 Subject: [PATCH 12/14] Remove issue related to CSV table focus --- app/templates/views/accessibility_statement.html | 5 ----- 1 file changed, 5 deletions(-) diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html index 421fca33f..be1706f90 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -39,7 +39,6 @@

    • low vision users cannot access the table we use to show CSV data when viewed at high zoom
      • -
    • keyboard-only and voice activation users cannot focus on the table we use to show CSV data
    • screen reader users may find the process of moving templates and folders confusing
    • one page links to a PDF document that is not fully accessible
    • screen readers users may be disorientated when pages load with the focus on a specific area
      • @@ -102,10 +101,6 @@ Low vision users cannot access the table we use to show CSV data when viewed at high zoom. This fails WCAG 1.4.10 success criteria (Reflow). We plan to fix this by the end of 2020.

      -

      - Keyboard-only and voice activation users cannot focus on the table we use to show CSV data. This fails WCAG 2.1.1 success criteria (Keyboard). 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 plan to fix this by November 2020.

      From 80c84f2f52740d6f578cabd6fd180e7242b76c78 Mon Sep 17 00:00:00 2001 From: Tom Byers Date: Wed, 23 Sep 2020 11:26:57 +0100 Subject: [PATCH 13/14] Make reference to status page a link Co-authored-by: Chris Hill-Scott --- app/templates/views/accessibility_statement.html | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/app/templates/views/accessibility_statement.html b/app/templates/views/accessibility_statement.html index be1706f90..cd867b5c0 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -141,7 +141,7 @@

    - 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 Web Content Accessibility Guidelines version 2.1 AA standard:

      @@ -176,4 +176,3 @@ This statement was prepared on 23 September 2020. It was last reviewed on 23 September 2020.

      {% endblock %} - From fb112bd5f76c82a11558951091393b961571e905 Mon Sep 17 00:00:00 2001 From: Tom Byers Date: Wed, 23 Sep 2020 11:27:31 +0100 Subject: [PATCH 14/14] Fix typo in status page issue Co-authored-by: Chris Hill-Scott --- 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 cd867b5c0..781674de4 100644 --- a/app/templates/views/accessibility_statement.html +++ b/app/templates/views/accessibility_statement.html @@ -148,7 +148,7 @@
    • an incorrect heading hierarchy which fails WCAG 2.1A 1.3.1 success criterion (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.1A 1.3.1 success criterion (Info and Relationships)
      • -
    • our status page ‘subscribe to updates’ link does not contain programmatically discernible link text – tThis fails WCAG 2.1A 1.3.1 success criterion (Info and Relationships)
      • +
    • 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)
    • 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)
    • 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)
    • 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)