darkhelm/notifications-admin
1
0
Fork 0
mirror of https://github.com/GSA/notifications-admin.git synced 2026-07-16 03:10:16 -04:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #3995 from alphagov/update-accessibility-statement

Browse Source 
Update accessibility statement with new issues
This commit is contained in:
Katie Smith
2021-08-13 16:46:48 +01:00
committed by GitHub
parent bb414ee3b9 7b49dbb236
commit 2a0181d909
1 changed files with 72 additions and 23 deletions
Download Patch File Download Diff File Expand all files Collapse all files

95
app/templates/views/accessibility_statement.html
View File

@@ -10,7 +10,7 @@
<h1 class="heading-large">Accessibility statement</h1>
<p class="govuk-body">
This accessibility statement applies to the www.notifications.service.gov.uk domain. It does not apply to the <a class="govuk-link" href="https://docs.notifications.service.gov.uk">GOV.UK Notify API documentation subdomain</a>.
This accessibility statement applies to the www.notifications.service.gov.uk domain. It does not apply to the <a class="govuk-link govuk-link--no-visited-state" href="https://docs.notifications.service.gov.uk">GOV.UK Notify API documentation subdomain</a>.
</p>
<p class="govuk-body">
@@ -29,7 +29,7 @@
</p>
<p class="govuk-body">
<a class="govuk-link" href="https://mcmw.abilitynet.org.uk">AbilityNet</a> has advice on making your device easier to use if you have a disability.
<a class="govuk-link govuk-link--no-visited-state" href="https://mcmw.abilitynet.org.uk">AbilityNet</a> has advice on making your device easier to use if you have a disability.
</p>
<h2 class="heading-medium">How accessible this website is</h2>
@@ -38,7 +38,14 @@
We know some parts of this website are not fully accessible:
</p>
<ul class="govuk-list govuk-list--bullet">
<li>screen reader users may find the process of moving templates and folders confusing</li>
<li>the ‘upload a file’ button may cause issues for some users</li>
<li>if a team adds template folders, screen readers may announce the page heading in a confusing way</li>
<li>the ‘copy to clipboard’ button does not work with some screen readers</li>
<li>Windows users cannot view our icons in high contrast mode</li>
<li>validation errors may be confusing for screen reader users</li>
<li>the way that screen readers announce the different regions of our pages can be confusing</li>
<li>choosing the date and time to send a message may be hard for some screen reader users</li>
<li>screen reader users may find it expand or collapse groups of checkboxes</li>
<li>one page links to a PDF document that is not fully accessible</li>
<li>the Notify status page has several accessibility issues</li>
</ul>
@@ -46,11 +53,11 @@
<p class="govuk-body">
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.
</p>
<h2 class="heading-medium">Feedback and contact information</h2>
<p class="govuk-body">
If you need any part of this service in a different format like large print, audio recording or braille, <a class="govuk-link" href="https://www.notifications.service.gov.uk/support">contact the GOV.UK Notify team</a>.
If you need any part of this service in a different format like large print, audio recording or braille, <a class="govuk-link govuk-link--no-visited-state" href="https://www.notifications.service.gov.uk/support">contact the GOV.UK Notify team</a>.
</p>
<p class="govuk-body">
@@ -60,7 +67,7 @@
<h2 class="heading-medium">Reporting accessibility problems with this website</h2>
<p class="govuk-body">
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, <a class="govuk-link" href="https://www.notifications.service.gov.uk/support">contact the GOV.UK Notify team</a>.
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, <a class="govuk-link govuk-link--no-visited-state" href="https://www.notifications.service.gov.uk/support">contact the GOV.UK Notify team</a>.
</p>
<h2 class="heading-medium">Enforcement procedure</h2>
@@ -70,7 +77,7 @@
</p>
<p class="govuk-body">
Find out how to <a class="govuk-link" href="https://www.notifications.service.gov.uk/support">contact the GOV.UK Notify team</a>.
Find out how to <a class="govuk-link govuk-link--no-visited-state" href="https://www.notifications.service.gov.uk/support">contact the GOV.UK Notify team</a>.
</p>
<h2 class="heading-medium">Technical information about this website’s accessibility</h2>
@@ -80,7 +87,7 @@
</p>
<p class="govuk-body">
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.
</p>
<h2 class="heading-medium">Non-accessible content</h2>
@@ -92,9 +99,51 @@
<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 2.1 success criteria 4.1.2 (Name, role, value)</a>.</p>
The following content on the Notify website is not compliant with the WCAG version 2.1 AA standard:
</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.
<ul class="govuk-list govuk-list--bullet">
<li>
the (before <abbr title="HyperText Markup Language">HTML</abbr>) code for the ‘upload a file’ button may cause issues for assistive technology users - this fails <a class="govuk-link govuk-link--no-visited-state" href="https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships">success criterion 1.3.1: info and relationships</a>
</li>
<li>
the JAWS and NVDA screen readers do not announce the ‘copy to clipboard’ button - this fails <a class="govuk-link govuk-link--no-visited-state" href="https://www.w3.org/WAI/WCAG21/Understanding/status-messages.html">success criterion 4.1.3: status messages</a>
</li>
<li>
some icons do not appear when using high contrast mode on Windows - this fails <a class="govuk-link govuk-link--no-visited-state" href="https://www.w3.org/WAI/WCAG21/Understanding/visual-presentation.html">success criterion 1.4.8: visual presentation</a>
</li>
</ul>
<p class="govuk-body">
We expect to fix these issues by the end of October 2021.
</p>
<h3 class="heading-small">Problems with using the interface</h3>
<p class="govuk-body">
We’ve identified the following problems with the user interface:
</p>
<ul class="govuk-list govuk-list--bullet">
<li>
the JAWS screen reader announces template folder page headings as multiple sentences
</li>
<li>
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
</li>
<li>
the way we label the different regions of our pages is confusing for screen reader users
</li>
<li>
choosing the date and time you want to send a message using a screen reader can be confusing
</li>
<li>
expanding and collapsing groups of checkboxes using a screen reader can be confusing
</li>
</ul>
<p class="govuk-body">
We hope to fix these issues by the end of December 2021.
</p>
<h3 class="heading-small">
@@ -117,7 +166,7 @@
</p>
<p class="govuk-body">
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 the end of 2021.
</p>
<h3 class="heading-small">
@@ -125,19 +174,19 @@
</h3>
<p class="govuk-body">
The following content on the <a class="govuk-link" href="https://status.notifications.service.gov.uk/">Notify status page</a> is not compliant with the Web Content Accessibility Guidelines version 2.1 AA standard:
The following content on the <a class="govuk-link govuk-link--no-visited-state" href="https://status.notifications.service.gov.uk/">Notify status page</a> is not compliant with the WCAG version 2.1 AA standard:
</p>
<ul class="govuk-list govuk-list--bullet">
<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>an incorrect heading hierarchy which fails <a class="govuk-link govuk-link--no-visited-state" href="https://www.w3.org/TR/WCAG21/#info-and-relationships">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 <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>
<li>our status incident page is missing the main heading and the status home page has an incorrect heading hierarchy – this fails <a class="govuk-link govuk-link--no-visited-state" href="https://www.w3.org/TR/WCAG21/#info-and-relationships">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 class="govuk-link govuk-link--no-visited-state" href="https://www.w3.org/TR/WCAG21/#info-and-relationships">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 class="govuk-link govuk-link--no-visited-state" href="https://www.w3.org/TR/WCAG21/#info-and-relationships">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 class="govuk-link govuk-link--no-visited-state" href="https://www.w3.org/TR/WCAG21/#name-role-value">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 class="govuk-link govuk-link--no-visited-state" href="https://www.w3.org/TR/WCAG21/#contrast-minimum">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 class="govuk-link govuk-link--no-visited-state" href="https://www.w3.org/TR/WCAG21/#link-purpose-in-context">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 class="govuk-link govuk-link--no-visited-state" href="https://www.w3.org/TR/WCAG21/#status-messages">success criterion 4.1.3: status messages</a></li>
</ul>
<p class="govuk-body">
@@ -149,7 +198,7 @@
</h2>
<p class="govuk-body">
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.
</p>
<p class="govuk-body">
@@ -157,6 +206,6 @@
</p>
<p class="govuk-body">
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.
</p>
{% endblock %}