+ 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: +
++ The text should be clear and simple to understand. +
+ ++ AbilityNet has advice on making your device easier to use if you have a disability. +
++ We know some parts of this website are not fully accessible: +
++ We know that the emails Notify sends are not fully accessible: +
++ If you need any part of this service in a different format like large print, audio recording or braille, contact the GOV.UK Notify team. +
+ ++ We’ll consider your request and get back to you within one working day. +
++ 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, contact: [provide both details of how to report these issues to your organisation, and contact details for the unit or person responsible for dealing with these reports]. +
++ 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). +
+ ++ Find out how to contact the GOV.UK Notify team. +
++ GDS is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. +
++ GOV.UK Notify is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below. +
+ ++ The content listed below is non-accessible for the following reasons. +
+ ++ Low vision users cannot access the table we use to show CSV data when viewed at high zoom. This fails WCAG 1.4.10 success criteria (Reflow). +
+ ++ Keyboard-only and voice activation users cannot focus on the table we use to show CSV data. This fails WCAG 2.1.1 success criteria (Keyboard). +
+ ++ Screen reader users may find the process of moving templates and folders confusing. This fails WCAG 4.1.2 success criteria (Name, role, value). +
+ ++ Screenreader users may find it confusing that a specific part of some pages is focused when they load. This fails WCAG 2.4.3 success criteria (Focus Order) +
+ ++ Some pages have links to PDF documents, and these PDF documents are not fully accessible. This is not a fail under any WCAG 2.1 success criterion. We provide the information contained in these PDFs in an accessible HTML format. +
+ ++ Some of our PDFs are essential to providing our services. For example, we have a PDF that shows the layout of our letter specification. We provide a written description of this information on an HTML page as an accessible alternative. +
+ ++ The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services. For example, we do not plan to fix [example of non-essential document]. +
+ ++ Any new PDFs or Word documents we publish will meet accessibility standards. +
+ ++ NVDA screen reader announces the URL of the GOV.UK logo image in emails when you view them in Microsoft Outlook +
+ ++ JAWS and NVDA screen readers announce extra spaces in emails when you view them in Microsoft Outlook +
+ ++ The Voiceover screen reader announces the hidden summary sentence in our emails when you open them in Apple Mail +
+ ++ 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). +
+ ++ 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. +
+ ++ This statement was prepared on 22 September 2020. It was last reviewed on 22 September 2020. +
{% endblock %}