notifications-admin/app/templates/views/accessibility_statement.html

{% extends "content_template.html" %}
{% from "components/service-link.html" import service_link %}

{% block per_page_title %}
  Accessibility statement
{% endblock %}

{% block content_column_content %}

  <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>.
  </p>

  <p class="govuk-body">
    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:
  </p>
  <ul class="govuk-list govuk-list--bullet">
    <li>change colours, contrast levels and fonts</li>
    <li>zoom in up to 300% without the text spilling off the screen</li>
    <li>navigate most of the website using just a keyboard</li>
    <li>navigate most of the website using speech recognition software</li>
    <li>listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)</li>
  </ul>

  <p class="govuk-body">
    The text should be clear and simple to understand.
  </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.
  </p>

  <h2 class="heading-medium">How accessible this website is</h2>

  <p class="govuk-body">
    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>one page links to a PDF document that is not fully accessible</li>
    <li>the Notify status page has several accessibility issues</li>
  </ul>

  <p class="govuk-body">
    We know that the emails Notify sends are not fully accessible:
  </p>
  <ul class="govuk-list govuk-list--bullet">
    <li>JAWS and NVDA screen readers announce extra spaces in emails when you view them in Microsoft Outlook</li>
  </ul>

  <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>.
  </p>

  <p class="govuk-body">
    We’ll consider your request and get back to you within one working day.
  </p>

  <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>.
  </p>

  <h2 class="heading-medium">Enforcement procedure</h2>

  <p class="govuk-body">
    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).
  </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>.
  </p>

  <h2 class="heading-medium">Technical information about this website’s accessibility</h2>

  <p class="govuk-body">
    GDS is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
  </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.
  </p>

  <h2 class="heading-medium">Non-accessible content</h2>

  <p class="govuk-body">
    The content listed below is non-accessible for the following reasons.
  </p>

  <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.
  </p>

  <h3 class="heading-small">
    PDFs and other documents
  </h3>

  <p class="govuk-body">
    One page links to a PDF document that is not fully accessible. This is not a fail under any WCAG 2.1 success criterion.</p>

  <p class="govuk-body">
    We provide a written description of the information in the PDF on an HTML page as an accessible alternative.
  </p>

  <h3 class="heading-small">
    Emails
  </h3>

  <p class="govuk-body">
    The JAWS and NVDA screen readers announce extra spaces in emails when viewed in Microsoft Outlook.
  </p>

  <p class="govuk-body">
    We’ll continue to investigate the cause of these issues and, if possible, fix them by March 2021.
  </p>

  <h3 class="heading-small">
    Status page
  </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:
  </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>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>
  </ul>

  <p class="govuk-body">
    We plan to have the status page issues addressed by the current supplier or move to an alternative supplier in 2021.
  </p>

  <h2 class="heading-medium">
    How we tested this service
  </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).
  </p>

  <p class="govuk-body">
    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.
  </p>

  <p class="govuk-body">
    This statement was prepared on 23 September 2020. It was last reviewed on 22 October 2020.
  </p>
{% endblock %}