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

Merge pull request #3769 from alphagov/update-accessibility-statement-with-dac-testing

Browse Source 
Update issue with moving templates/folders
This commit is contained in:
Tom Byers
2021-01-14 15:06:51 +00:00
committed by GitHub
parent 248406938f a6e4022ce7
commit 81b576acad
1 changed files with 13 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -92,7 +92,9 @@
<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>. We plan to fix this by November 2020.
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>
<h3 class="heading-small">
@@ -127,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">
@@ -147,7 +149,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 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.
</p>
<p class="govuk-body">
@@ -155,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 %}