diff --git a/docs/_includes/components/button.html b/docs/_includes/components/button.html index 21f2ea2..bcb8caa 100644 --- a/docs/_includes/components/button.html +++ b/docs/_includes/components/button.html @@ -1,4 +1,4 @@ - {{ include.text }} diff --git a/docs/pages/footer/accessibility.md b/docs/pages/footer/accessibility.md index b0ab4e4..8b85aff 100644 --- a/docs/pages/footer/accessibility.md +++ b/docs/pages/footer/accessibility.md @@ -50,17 +50,6 @@ The following content is non-accessible for the following reasons. ### Non-compliance with the accessibility regulations -The NHS logo image in the header is missing an appropriate aria-label, making it hard for people with screen readers to understand what the image is. This fails WCAG 2.2 success criterion 1.1.1 (non-text content). - -We plan to add an aria-label to this image in a future release. - -When using 'create and submit a template', people using screen readers may not understand the relationship of the template guidance to the main task of creating a template. Additionally, when the tables in the preview screens are resized, a logical tab order is not maintained. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships). - -In a future release we plan to: - -- amend the HTML structure to reflect the intended relationships between the guidance and the main task of creating a template -- ensure a logical tab order when the screen is resized - Autocomplete is turned off by default, making it harder to fill out any form elements when using 'create and submit a template'. This fails WCAG 2.2 success criterion 1.3.5 (identity input purpose). Autocomplete is turned off by default because the text a user enters into ‘create and submit a template’ will almost always be different for each submission. This makes autocomplete inappropriate for these fields. When we add new features that ask users for repeatable information, autocomplete will be enabled. diff --git a/docs/pages/get-started/get-started.md b/docs/pages/get-started/get-started.md index 81d31cd..58e14ce 100644 --- a/docs/pages/get-started/get-started.md +++ b/docs/pages/get-started/get-started.md @@ -11,23 +11,27 @@ permalink: /get-started/ ## 1. Check if NHS Notify is right for you -Use NHS Notify if your organisation or service sends: +You can only use NHS Notify if your organisation or service sends: -- [messages that are part of a campaign]({% link pages/using-nhs-notify/campaigns.md %}) -- [event based messages]({% link pages/using-nhs-notify/event-based-messaging.md %}) +- [event-based messages]({% link pages/using-nhs-notify/event-based-messaging.md %}) - [direct messages]({% link pages/using-nhs-notify/direct-messaging.md %}) +- [messages that are part of a campaign]({% link pages/using-nhs-notify/campaigns.md %}) + +You also need to have: -You may need to read our: +- funding or a budget agreed for sending messages +- a way to get the NHS numbers of your recipients +- technical or developer support to build your integration with NHS Notify + +You should also read our: - [terms and conditions (opens in a new tab)](https://digital.nhs.uk/services/nhs-notify/terms-and-conditions){:target="\_blank"} - [acceptable use policy (opens in a new tab)](https://digital.nhs.uk/services/nhs-notify/acceptable-use-policy){:target="\_blank"} - [privacy policy (opens in a new tab)](https://digital.nhs.uk/services/nhs-notify/transparency-notice){:target="\_blank"} -## 2. Register your interest with NHS Notify - -If you think NHS Notify is right for you, complete the following form to register your interest. This will open in a new tab. +## 2. Register your interest -We’ll contact you within 10 working days to find out more about your needs. +Complete the following form to register your interest with NHS Notify. This will open in a new tab. {% include components/button.html text="Register your interest"