Fix link markup

This commit is contained in:
karlchillmaid
2021-08-13 14:41:11 +01:00
committed by Katie Smith
parent 342e0e9d05
commit 7b49dbb236

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>
@@ -53,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">
@@ -67,7 +67,7 @@
<h2 class="heading-medium">Reporting accessibility problems with this website</h2>
<p class="govuk-body">
Were always looking to improve the accessibility of this website. If you find any problems not listed on this page or think were not meeting accessibility requirements, <a class="govuk-link" href="https://www.notifications.service.gov.uk/support">contact the GOV.UK Notify team</a>.
Were always looking to improve the accessibility of this website. If you find any problems not listed on this page or think were 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>
@@ -77,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 websites accessibility</h2>
@@ -104,13 +104,13 @@
<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 href="https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships">success criterion 1.3.1: info and relationships</a>
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 href="https://www.w3.org/WAI/WCAG21/Understanding/status-messages.html">success criterion 4.1.3: status messages</a>
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 href="https://www.w3.org/WAI/WCAG21/Understanding/visual-presentation.html">success criterion 1.4.8: visual presentation</a>
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>
@@ -174,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 WCAG 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">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">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>
<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">