Skip to content

Commit 630fd5f

Browse files
jakecosgrovejakecosgrove
authored
Accessibility statement, sitemap and other misc changes (#95)
* First draft accessibility statement and Jake first attempt at sitemap - cannot work out how to sort by section headings in each section * Commit adds: - sitemap page with automatically updating links - accessibility statement based on findings of audit - new item in roadmap about addressing accessibility issues in 'what we're working on now' * Alt text removed from decorative images on landing page Email address added to accessibility statement * Typo fixes * Dates added to accessibility statement * screen reader typo * alt-text removal for illustrative images on landing page * Emma 2i changes
1 parent 37e8631 commit 630fd5f

File tree

7 files changed

+183
-11
lines changed

7 files changed

+183
-11
lines changed

‎docs/_data/footer-navigation.yml‎

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
1-
#- title: Accessibility statement
2-
#link: /accessibility/
1+
- title: Accessibility statement
2+
link: /accessibility/
33

44
- title: Acceptable use policy
55
link: https://digital.nhs.uk/services/nhs-notify/acceptable-use-policy
@@ -10,5 +10,8 @@
1010
- title: Privacy
1111
link: https://digital.nhs.uk/services/nhs-notify/transparency-notice
1212

13+
- title: Sitemap
14+
link: /sitemap/
15+
1316
- title: Terms and conditions
1417
link: https://digital.nhs.uk/services/nhs-notify/terms-and-conditions

‎docs/_data/home/find-out-more.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,4 +2,4 @@ heading: Find out how you can start using NHS Notify
22
description: |
33
NHS England organisations and services that support direct care can register their interest and get started with NHS Notify.
44
image: CTA-register-your-interest.svg
5-
image_alt: A graphic of a laptop screen with a draft email open.
5+
image_alt: ""

‎docs/_data/home/heading.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,4 +3,4 @@ description: |
33
You can use NHS Notify if you work in or with NHS England to support patient care.
44
image: landing-main-image-2.svg
55
image_alt: |
6-
A graphic representation of NHS Notify's message channels: NHS App, email, text message and letter.
6+
""

‎docs/_data/home/how-it-works.yml‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,22 +6,22 @@
66
- text messages (SMS)
77
- letters
88
image: 1-write-your-message.svg
9-
image_alt: A screenshot showing how you write messages using NHS Notify's user interface.
9+
image_alt: ""
1010

1111
- heading: Tell us who to message using their NHS number
1212
description: |
1313
You only need a person’s NHS number to send them messages.
1414
image: choose-your-recipients-no-dob.svg
15-
image_alt: A screenshot of computer code showing how you provide your recipients.
15+
image_alt: ""
1616

1717
- heading: Plan how your messages will be sent
1818
description: |
1919
Set up routing plans to decide how your messages will be sent to recipients.
2020
image: 3-plan-your-messages.svg
21-
image_alt: A graphic of a phone, laptop and letter (numbered 1, 2 and 3 in that order) to show that you can send messages with each message channel in a specific order.
21+
image_alt: ""
2222

2323
- heading: See how your messages perform
2424
description: |
2525
Track how many messages you've sent and find out which ones are not being delivered.
2626
image: 4-see-message-performance.svg
27-
image_alt: A screenshot of NHS Notify showing counts of NHS App messages and text messages that have been sent.
27+
image_alt: ""

‎docs/pages/features/roadmap.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ You can [contact us]({% link pages/support/support.md %}) if you:
2626
- Improve onboarding for new users
2727
- Increase print capacity and resilience by bringing in an additional supplier
2828
- Let users create and manage their own templates
29-
- Publish a new website with information about NHS Notify
29+
- Fix accessibility issues in the upcoming 'create and submit a template' interface
3030
- Provide real-time message statuses to show whether messages have been successfully delivered
3131
- Show users which recipients have NHS App accounts and notifications enabled
3232
- Let users subscribe to more detailed NHS APP message statuses

‎docs/pages/footer/accessibility.md‎

Lines changed: 88 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,94 @@
33
# To modify the layout, see https://jekyllrb.com/docs/themes/#overriding-theme-defaults
44

55
layout: no-nav-page
6-
title: Accessibility
6+
title: Accessibility statement
77
permalink: /accessibility/
88
---
99

10-
This page will contain the accessibility information for the NHS Notify Web Template Management UI.
10+
This accessibility statement applies to [notify.nhs.uk](https://notify.nhs.uk/).
11+
12+
It does not apply to:
13+
14+
- [NHS Notify API catalogue page](https://digital.nhs.uk/developer/api-catalogue/nhs-notify)
15+
- [NHS Notify MESH catalogue page](https://digital.nhs.uk/developer/api-catalogue/nhs-notify-mesh)
16+
- [NHS Notify service catalogue page](https://digital.nhs.uk/services/nhs-notify)
17+
18+
This website is run by the NHS Notify team at NHS England. We want as many people as possible to be able to use this website. For example, that means you should be able to:
19+
20+
- change colours, contrast levels and fonts using browser or device settings
21+
- zoom in up to 400% without the text spilling off the screen
22+
- navigate most of the website using a keyboard or speech recognition software
23+
- listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
24+
25+
We’ve also made the website text as simple as possible to understand.
26+
27+
[AbilityNet](https://mcmw.abilitynet.org.uk/) has advice on making your device easier to use if you have a disability.
28+
29+
## Feedback and contact information
30+
31+
If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact us by sending an email to <[email protected]>.
32+
33+
## Enforcement procedure
34+
35+
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)](https://www.equalityadvisoryservice.com/).
36+
37+
## Technical information about this website's accessibility
38+
39+
NHS Notify is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
40+
41+
## Compliance status
42+
43+
The website has been tested against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.
44+
45+
This website is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed in the next section.
46+
47+
## Non-accessible content
48+
49+
The following content is non-accessible for the following reasons.
50+
51+
### Non-compliance with the accessibility regulations
52+
53+
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).
54+
55+
We plan to add an aria-label to this image in a future release.
56+
57+
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).
58+
59+
In a future release we plan to:
60+
61+
- amend the HTML structure to reflect the intended relationships between the guidance and the main task of creating a template
62+
- ensure a logical tab order when the screen is resized
63+
64+
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).
65+
66+
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.
67+
68+
Pages within 'create a submit a template' are missing meaningful titles, making it difficult for people to:
69+
70+
- easily identify if the information on that page is relevant to their needs
71+
- differentiate content when multiple web pages are open
72+
- navigate between web pages when using audio assistive technologies
73+
74+
This fails WCAG 2.2 success criterion 2.4.2 (page titles).
75+
76+
We plan to add page titles that are unique and reflect the purpose of each page in a future release.
77+
78+
Some links such as 'copy' and 'delete' are ambiguous for users, making it difficult for screen reader users to determine what items they are copying or deleting. This fails WCAG 2.2 success criterion 2.4.4 (link purpose).
79+
80+
We plan to add hidden text that can be read by screen readers and better describes what items are being copied or deleted in a future release.
81+
82+
When using a screen reader, it is not clear that the markdown examples in 'create and submit a template' are examples that can be copied. This fails WCAG 2.2 success criterion 2.4.6 (headings and labels).
83+
84+
n a future release, we plan to add hidden text that can be read by screen readers and describes that the markdown examples are examples that can be copied.
85+
86+
## What we're doing to improve accessibility
87+
88+
Our [roadmap]({% link pages/features/roadmap.md %}) shows how and when we plan to improve accessibility on this website.
89+
90+
## Preparation of this accessibility statement
91+
92+
This statement was prepared on Friday 7 March 2024. It was last reviewed on Friday 7 March 2024.
93+
94+
This website was last tested on Thursday 27 February 2025 against the WCAG 2.2 AA standard.
95+
96+
The test was carried out by the NHS Notify research and development team. The most viewed pages were tested using automated testing tools by our team. A further audit of the website was carried out to the WCAG 2.2 AA standard.

‎docs/pages/sitemap.html‎

Lines changed: 83 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
---
2+
permalink: /sitemap.html
3+
layout: default
4+
title: Sitemap
5+
---
6+
7+
<div class="nhsuk-width-container">
8+
<main class="nhsuk-main-wrapper" id="maincontent" role="main">
9+
<div class="nhsuk-grid-row">
10+
<div class="nhsnotify-pane__main-content nhsuk-grid-column-three-quarters">
11+
12+
<h1>{{page.title}}</h1>
13+
14+
<!-- Features -->
15+
<h2 class="nhsuk-heading-l"><a class="nhsuk-link" href="{{site.baseurl}}/features">Features</a></h2>
16+
17+
<ul class="nhsuk-list">
18+
{% for page in site.pages %}
19+
{% if page.parent == "Features" %}
20+
<li>
21+
<a class="nhsuk-link" href="{{ page.url }}">{{page.title}}</a>
22+
</li>
23+
{% endif %}
24+
{% endfor %}
25+
</ul>
26+
27+
<!-- Pricing -->
28+
<h2 class="nhsuk-heading-l"><a class="nhsuk-link" href="{{site.baseurl}}/pricing">Pricing</a></h2>
29+
30+
<ul class="nhsuk-list">
31+
{% for page in site.pages %}
32+
{% if page.parent == "Pricing" %}
33+
<li>
34+
<a class="nhsuk-link" href="{{ page.url }}">{{page.title}}</a>
35+
</li>
36+
{% endif %}
37+
{% endfor %}
38+
</ul>
39+
40+
<!-- Using NHS Notify -->
41+
<h2 class="nhsuk-heading-l"><a class="nhsuk-link" href="{{site.baseurl}}/using-nhs-notify">Using NHS Notify</a>
42+
</h2>
43+
44+
<ul class="nhsuk-list">
45+
{% for page in site.pages %}
46+
{% if page.parent == "Using NHS Notify" %}
47+
<li>
48+
<a class="nhsuk-link" href="{{ page.url }}">{{page.title}}</a>
49+
</li>
50+
{% endif %}
51+
{% endfor %}
52+
</ul>
53+
54+
<!-- Support -->
55+
<h2 class="nhsuk-heading-l"><a class="nhsuk-link" href="{{site.baseurl}}/support">Support</a></h2>
56+
57+
<ul class="nhsuk-list">
58+
{% for page in site.pages %}
59+
{% if page.parent == "Support" %}
60+
<li>
61+
<a class="nhsuk-link" href="{{ page.url }}">{{page.title}}</a>
62+
</li>
63+
{% endif %}
64+
{% endfor %}
65+
</ul>
66+
67+
<!-- Get started -->
68+
<h2 class="nhsuk-heading-l"><a class="nhsuk-link" href="{{site.baseurl}}/get-started">Get started</a></h2>
69+
70+
<ul class="nhsuk-list">
71+
{% for page in site.pages %}
72+
{% if page.parent == "Get started" %}
73+
<li>
74+
<a class="nhsuk-link" href="{{ page.url }}">{{page.title}}</a>
75+
</li>
76+
{% endif %}
77+
{% endfor %}
78+
</ul>
79+
80+
</div>
81+
</div>
82+
</main>
83+
</div>

0 commit comments

Comments
 (0)