darkhelm/notifications-admin
1
0
Fork 0
mirror of https://github.com/GSA/notifications-admin.git synced 2026-06-20 05:02:30 -04:00
Code Issues Packages Projects Releases Wiki Activity

Update success criterion and review date

Browse Source
This commit is contained in:
karlchillmaid
2021-08-13 12:06:18 +01:00
committed by Katie Smith
parent ab132bab2a
commit 18312cfdaa
1 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -166,19 +166,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" 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 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 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 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 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 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 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 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 href="https://www.w3.org/TR/WCAG21/#status-messages">success criterion 4.1.3: status messages</a></li>
</ul>
<p class="govuk-body">
@@ -198,6 +198,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 %}