Skip to content

Commit cf5cc29

Browse files
jakecosgrovejakecosgrove
authored
First draft accessibility statement and Jake first attempt at sitemap - cannot work out how to sort by section headings in each section
1 parent e642f7a commit cf5cc29

File tree

3 files changed

+188
-4
lines changed

3 files changed

+188
-4
lines changed

‎docs/_data/footer-navigation.yml‎

Lines changed: 2 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

‎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 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 our next 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 our next 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 as what a user will enter into 'create and submit a template' will almost always be different for each submission, making autocomplete for these fields inappropriate. 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 our next 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 that better describes what items are being copied or deleted in our next release.
81+
82+
When using a screenreader, 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+
We plan to add hidden text that can be read by screen readers that 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 [date when it was first published]. It was last reviewed on [date when it was first published].
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: 98 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,98 @@
1+
---
2+
permalink: /sitemap.html
3+
layout: default
4+
title: Sitemap
5+
---
6+
7+
{% assign current_dir = page.dir %}
8+
{% assign paths = page.dir | split: "/" %}
9+
{% assign parent_dir = paths[1] %}
10+
11+
{%-
12+
assign nav_pages = site.pages
13+
| where_exp: "item", "item.dir contains parent_dir"
14+
-%}
15+
16+
{% assign first_level_dir = parent_dir | prepend: '/' | append: '/' %}
17+
{%-
18+
assign first_level = nav_pages
19+
| where_exp: "item", "item.dir == first_level_dir"
20+
-%}
21+
22+
<div class="nhsuk-width-container">
23+
<main class="nhsuk-main-wrapper" id="maincontent" role="main">
24+
<div class="nhsuk-grid-row">
25+
<div class="nhsnotify-pane__main-content nhsuk-grid-column-three-quarters">
26+
27+
<h1>{{page.title}}</h1>
28+
29+
<!-- Features -->
30+
<h2 class="nhsuk-heading-l"><a class="nhsuk-link" href="{{site.baseurl}}/features">Features</a></h2>
31+
32+
<ul class="nhsuk-list">
33+
{% for page in site.pages %}
34+
{% if page.parent == "Features" %}
35+
<li>
36+
<a class="nhsuk-link" href="{{ page.url }}">{{page.title}}</a>
37+
</li>
38+
{% endif %}
39+
{% endfor %}
40+
</ul>
41+
42+
<!-- Pricing -->
43+
<h2 class="nhsuk-heading-l"><a class="nhsuk-link" href="{{site.baseurl}}/pricing">Pricing</a></h2>
44+
45+
<ul class="nhsuk-list">
46+
{% for page in site.pages %}
47+
{% if page.parent == "Pricing" %}
48+
<li>
49+
<a class="nhsuk-link" href="{{ page.url }}">{{page.title}}</a>
50+
</li>
51+
{% endif %}
52+
{% endfor %}
53+
</ul>
54+
55+
<!-- Using NHS Notify -->
56+
<h2 class="nhsuk-heading-l"><a class="nhsuk-link" href="{{site.baseurl}}/using-nhs-notify">Using NHS Notify</a>
57+
</h2>
58+
59+
<ul class="nhsuk-list">
60+
{% for page in site.pages %}
61+
{% if page.parent == "Using NHS Notify" %}
62+
<li>
63+
<a class="nhsuk-link" href="{{ page.url }}">{{page.title}}</a>
64+
</li>
65+
{% endif %}
66+
{% endfor %}
67+
</ul>
68+
69+
<!-- Support -->
70+
<h2 class="nhsuk-heading-l"><a class="nhsuk-link" href="{{site.baseurl}}/support">Support</a></h2>
71+
72+
<ul class="nhsuk-list">
73+
{% for page in site.pages %}
74+
{% if page.parent == "Support" %}
75+
<li>
76+
<a class="nhsuk-link" href="{{ page.url }}">{{page.title}}</a>
77+
</li>
78+
{% endif %}
79+
{% endfor %}
80+
</ul>
81+
82+
<!-- Get started -->
83+
<h2 class="nhsuk-heading-l"><a class="nhsuk-link" href="{{site.baseurl}}/get-started">Get started</a></h2>
84+
85+
<ul class="nhsuk-list">
86+
{% for page in site.pages %}
87+
{% if page.parent == "Get started" %}
88+
<li>
89+
<a class="nhsuk-link" href="{{ page.url }}">{{page.title}}</a>
90+
</li>
91+
{% endif %}
92+
{% endfor %}
93+
</ul>
94+
95+
</div>
96+
</div>
97+
</main>
98+
</div>

0 commit comments

Comments
 (0)