Skip to content

Commit b07f0d2

Browse files
acerathereinspirative-nhs-nviracerathereinspirative-nhs-nvir
committed
VIA-396 SB Update accessibility content.
1 parent 3795087 commit b07f0d2

File tree

1 file changed

+105
-245
lines changed
  • src/app/our-policies/accessibility

1 file changed

+105
-245
lines changed

‎src/app/our-policies/accessibility/page.tsx‎

Lines changed: 105 additions & 245 deletions
Original file line numberDiff line numberDiff line change
@@ -12,252 +12,112 @@ const AccessibilityStatement = () => {
1212

1313
<BackLink />
1414
<MainContent>
15-
<h1>Accessibility statement</h1>
16-
<p>This accessibility statement applies to the Check and book an RSV vaccination service.</p>
17-
<p>We want as many people as possible to be able to use this service. This means you should be able to:</p>
18-
<ul>
19-
<li>change colours, contrast levels and fonts using browser functionality</li>
20-
<li>zoom in up to 400 per cent without the text spilling off the screen</li>
21-
<li>navigate most of the website using just a keyboard</li>
22-
<li>navigate most of the website using speech recognition software</li>
23-
<li>
24-
interact with most of the website using a screen reader (including recent versions of JAWS, NVDA and
25-
VoiceOver)
26-
</li>
27-
</ul>
28-
<p>We also try to make the content as simple as possible to understand.</p>
29-
<p>
30-
If you have a disability,{" "}
31-
<a href="https://mcmw.abilitynet.org.uk/" target={"_blank"}>
32-
search AbilityNet for &#34;how to&#34; guides
33-
</a>{" "}
34-
to make your device easier to use.
35-
</p>
36-
<h2>How accessible this website is</h2>
37-
<p>TBD</p>
15+
<div className="app-dynamic-page-title nhsuk-u-margin-bottom-5 ">
16+
<h1 className="app-dynamic-page-title__heading">
17+
Accessibility statement for Check and book an RSV vaccination
18+
</h1>
19+
</div>
3820

39-
<h2>Feedback and contact information</h2>
40-
<p>
41-
If you have an accessibility query you can{" "}
42-
<a href="#" target={"_blank"}>
43-
give feedback about the NHS website
44-
</a>
45-
, including:
46-
</p>
47-
<ul>
48-
<li>if you have any problems accessing information or using this website</li>
49-
<li>if you have any positive feedback about this website&#39;s accessibility</li>
50-
</ul>
51-
<p>We aim to respond in 5 working days.</p>
52-
<h3>Alternative formats</h3>
53-
<p>We&#39;ve designed our content to be as accessible as possible.</p>
54-
<p>
55-
If you need information on this website in a different format, like accessible PDF, large print, easy read,
56-
audio recording or Braille, please{" "}
57-
<a href="#" target={"_blank"}>
58-
give feedback about this service
59-
</a>
60-
.
61-
</p>
62-
<p>We&#39;ll consider your request and get back to you in 10 working days.</p>
63-
<h3>Reporting accessibility problems with this website</h3>
64-
<p>
65-
We&#39;re always looking to improve the accessibility of this website. If you find any problems not listed on
66-
this page or think we&#39;re not meeting accessibility requirements, please{" "}
67-
<a href="#" target={"_blank"}>
68-
give feedback about this service
69-
</a>
70-
. This helps us improve.
71-
</p>
72-
<h2>Enforcement procedure</h2>
73-
<p>
74-
If you contact us with a complaint and you are not happy with our response,{" "}
75-
<a href="https://www.equalityadvisoryservice.com/" target={"_blank"}>
76-
contact the Equality Advisory and Support Service (EASS)
77-
</a>
78-
.
79-
</p>
80-
<p>
81-
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the{" "}
82-
<a href="https://www.legislation.gov.uk/uksi/2018/952/contents/made" target={"_blank"}>
83-
Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 on
84-
legislation.gov.uk
85-
</a>{" "}
86-
(the &#34;accessibility regulations&#34;).
87-
</p>
88-
<h2>Technical information about this website&#39;s accessibility</h2>
89-
<p>We&#39;re committed to making this website accessible, in accordance with the accessibility regulations.</p>
90-
<h3>Compliance status</h3>
91-
<p>
92-
TBD
93-
<br />
94-
This website is partially compliant with the{" "}
95-
<a href="https://www.w3.org/TR/WCAG22/" target={"_blank"}>
96-
Web Content Accessibility Guidelines (WCAG) version 2.2
97-
</a>{" "}
98-
AA standard, due to the non-compliances listed below.
99-
</p>
100-
<h2>Non-accessible content</h2>
101-
<p>
102-
The content that is not accessible is listed below together with an explanation and reference to the relevant
103-
WCAG section.
104-
</p>
105-
<h3>Non-compliance with the accessibility regulations</h3>
106-
<h4>Forms</h4>
107-
<h5>Service search (newer templates)</h5>
108-
<ul>
109-
<li>
110-
Help and error information is not announced automatically to screen readers (Info and relationships 1.3.1)
111-
</li>
112-
<li>Form labels are missing or broken (Info and relationships 1.3.1)</li>
113-
<li>
114-
Some messages are not automatically announced to users of assistive technology (Error identification 3.3.1)
115-
</li>
116-
<li>The search placeholder text is low contrast (Contrast (minimum) 1.4.3)</li>
117-
</ul>
118-
<h5>Podcasts</h5>
119-
<ul>
120-
<li>
121-
A text alternative (transcript) for audio-only content has not been provided for podcast content (Audio only
122-
1.2.1)
123-
</li>
124-
</ul>
125-
<h4>PDFs</h4>
126-
<ul>
127-
<li>
128-
The structure of the content is not always available to assistive technology, which makes the content
129-
difficult to understand and navigate for users of screen readers (Info and relationships 1.3.1)
130-
</li>
131-
<li>
132-
The reading order of the content is not always logical, which means some content does not make sense when
133-
read out by text-to-speech software (Meaningful sequence 1.3.2)
134-
</li>
135-
<li>
136-
Images do not always have text alternatives, which means some content is not available when using
137-
text-to-speech software (Text alternatives 1.1.1)
138-
</li>
139-
</ul>
140-
<h4>3rd-party tools and systems</h4>
141-
<p>There are several issues relating to the Qualtrics survey component. These include:</p>
142-
<ul>
143-
<li>
144-
Users require a specific sensory ability to interact with content. This fails under 1.3.3 Sensory
145-
Characteristics (Level A).
146-
</li>
147-
<li>
148-
When text properties are set by the user, there is no change in the appearance of text. This fails under
149-
1.4.12 Text Spacing (Level AA).
150-
</li>
151-
</ul>
152-
<p>
153-
The Qualtrics component is a third-party component. We have reported the issues and asked for updates.
154-
Qualtrics is expected to fix them at some point, but currently a specific date has not been provided.
155-
</p>
156-
<p>Some further issues relate to the Microsoft Azure B2C Login system. These include:</p>
157-
<ul>
158-
<li>
159-
Autocomplete attribute is missing or inactive on some fields. This fails under 1.3.1 Info and Relationships
160-
(Level A) and 1.5.3 Identify Input Purpose (Level AA).
161-
</li>
162-
<li>
163-
Error messages are not associated with form fields. This fails under 3.3.1 Error Identification (Level A);
164-
3.3.3 Error Suggestion (Level AA); and 4.1.3 Status Messages (Level AA).
165-
</li>
166-
<li>Positive tab index integer used on a component. This fails under 2.4.3 Focus Order (Level A).</li>
167-
</ul>
168-
<p>
169-
Tickets for these issues have been raised with Microsoft. Discussions are ongoing to resolve these issues.
170-
</p>
171-
<h4>
172-
<strong>Profile Manager</strong>
173-
</h4>
174-
<ul>
175-
<li>
176-
The same heading is duplicated at heading level 1 (H1) and heading level 2 (H2). This fails 1.3.1 Info and
177-
Relationships (Level A) and 2.4.6 Headings and Labels (Level AA).
178-
</li>
179-
<li>
180-
Error messages are not associated with the relevant form field. This fails under 3.3.1 Error Identification
181-
(Level A).
182-
</li>
183-
<li>
184-
Users cannot extend their session and are automatically logged out after 15 minutes. This fails under 2.2.1
185-
Timing Adjustable (Level A).
186-
</li>
187-
</ul>
188-
<h4>Content visibility</h4>
189-
<ul>
190-
<li>
191-
Low contrast focus indication style on: links, buttons, form fields, and search components (Non-text
192-
contrast 1.4.11)
193-
</li>
194-
</ul>
195-
<h4>Screen readers</h4>
196-
<ul>
197-
<li>
198-
Inaccessible HTML such as empty ARIA (accessible rich internet applications) landmarks, incorrect or broken
199-
instances of the ARIA attributes and empty lists or lists with 1 item (Info and relationships 1.3.1)
200-
</li>
201-
<li>Form labels are missing or broken (Info and relationships 1.3.1)</li>
202-
<li>Anchor tags contain empty content (Meaningful sequence 1.3.2)</li>
203-
</ul>
204-
<h3>Content that&#39;s not within the scope of the accessibility regulations</h3>
205-
<h4>PDFs and other documents</h4>
206-
<p>
207-
Many of our older PDFs do not meet accessibility standards. The accessibility regulations do not require us to
208-
fix PDFs or other documents published before 23 September 2018 if they&#39;re not essential to providing our
209-
services. We do have plans to remove or replace some of the PDFs with more accessible content alternatives.
210-
Wherever possible, we avoid PDFs. Instead, we create content as structured web pages in HTML
211-
</p>
212-
<h4>Videos</h4>
213-
<p>
214-
All video published after 23 September 2020 meets WCAG AA standard, which includes captions, transcripts, and
215-
audio descriptions. As part of our ongoing transformation work, we are continuously improving older videos to
216-
meet the same standard.
217-
</p>
218-
<h2>What we&#39;re doing to improve accessibility</h2>
219-
<p>
220-
We have published tools and guidance on accessibility in the{" "}
221-
<a href="https://service-manual.nhs.uk/" target={"_blank"}>
222-
NHS digital service manual
223-
</a>{" "}
224-
based on extensive testing. The service manual helps our teams build products and services to meet the same
225-
accessibility standards.
226-
</p>
227-
<p>
228-
At NHS England, creating an accessible service is a team effort. We want our teams to make accessible services
229-
by:
230-
</p>
231-
<ul>
232-
<li>considering accessibility at the start of their project, and throughout</li>
233-
<li>making accessibility the whole team&#39;s responsibility</li>
234-
<li>researching with disabled users</li>
235-
<li>using a library of accessible components and patterns</li>
236-
<li>carrying out regular accessibility audits and testing</li>
237-
<li>designing and building to level AA of WCAG 2.2 – which is NHS England policy</li>
238-
</ul>
239-
<p>
240-
As part of this commitment, we have set up a cross-functional accessibility working group to make sure that
241-
accessibility remains at the core of everything we do.
242-
</p>
243-
<p>
244-
We are making sure that accessibility issues highlighted in this statement are being prioritised and fixed.
245-
Measures include:
246-
</p>
247-
<ul>
248-
<li>all videos to be made AA standard when they are reviewed after 23 September 2020</li>
249-
<li>
250-
continued accessibility fixes to the NHS website video player to make sure it adheres to WCAG AA standard.
251-
</li>
252-
<li>a principle to move away from new content being produced in PDF</li>
253-
<li>plans to remove or replace older PDFs with more accessible content</li>
254-
<li>ongoing improvements to the NHS design system with a focus on accessibility</li>
255-
<li>prioritising accessibility remedial work in all new development and improvement projects</li>
256-
<li>working with suppliers to improve the accessibility of their products</li>
257-
</ul>
258-
<h2>Preparation of this accessibility statement</h2>
259-
<p>This statement was updated in May 2025.</p>
260-
<p>TBD</p>
21+
<article>
22+
<section>
23+
<p>
24+
This accessibility statement applies to using the service on an iOS or Android device. It also applies
25+
when you access the same services by logging in through the NHS website in a web browser. When we publish
26+
new content, we will make sure that all features meet accessibility standards. We will update this
27+
statement with our progress on fixing any issues.
28+
</p>
29+
<h2>
30+
<b>Using accessibility settings on your device</b>
31+
</h2>
32+
<p>
33+
On a phone or tablet you can use the built-in{" "}
34+
<a href="https://www.apple.com/uk/accessibility/iphone/">Apple iOS</a> or{" "}
35+
<a href="https://support.google.com/accessibility/android/answer/6006564?hl=en-GB">Android</a>{" "}
36+
accessibility settings to make some parts of this service more accessible.
37+
<br />
38+
<br /> You can also log in from the NHS website. By changing the settings on your web browser or computer
39+
you should be able to:
40+
</p>
41+
<ul>
42+
<li>change colours, contrast levels and fonts</li>
43+
<li>zoom in up to 200% with the text staying visible on the screen</li>
44+
<li>navigate most of the website using just a keyboard</li>
45+
<li>navigate most of the website using speech recognition software</li>
46+
<li>
47+
listen to most of the website using a screen reader, including the latest versions of JAWS, NVDA and
48+
VoiceOver
49+
</li>
50+
</ul>
51+
<p>
52+
<a href="https://mcmw.abilitynet.org.uk/">AbilityNet</a> has advice to help you make your device easier to
53+
use if you have a disability.
54+
</p>
55+
<p>
56+
You need to create an NHS login to use this service. You can read the{" "}
57+
<a href="https://access.login.nhs.uk/accessibility">NHS login accessibility statement</a>.
58+
</p>
59+
<h2>How accessible is Check and book an RSV vaccination?</h2>
60+
<p>
61+
We regularly test our content to Web Content Accessibility Guidelines (WCAG) 2.2 on both mobile and
62+
desktop devices. We follow the NHS service manual guidance on{" "}
63+
<a href="https://service-manual.nhs.uk/accessibility">accessible design</a>. We also try to make text as
64+
simple as possible to understand, following the{" "}
65+
<a href="https://service-manual.nhs.uk/content">NHS style guide</a>.
66+
</p>
67+
<p>Our latest accessibility audit showed all pages in this service to be fully accessible.</p>
68+
69+
<h2>How to report accessibility problems or give feedback</h2>
70+
<p>
71+
If you find any problems not listed on this page or you think we&apos;re not meeting accessibility
72+
requirements, email <a href="mailto:[email protected]">[email protected]</a>. We aim
73+
to respond to all enquiries within 72 hours.
74+
</p>
75+
<p>
76+
If you need documents from your health record in a different format, ask your health professional for
77+
assistance. This service can only show the information provided by your health professional.
78+
</p>
79+
80+
<h3>Enforcement procedure</h3>
81+
<p>
82+
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the{" "}
83+
<a href="https://www.legislation.gov.uk/uksi/2018/952/contents/made">
84+
Public Sector Bodies (Website and Mobile Applications) (No.2) Accessibility Regulations 2018 (the
85+
&apos;accessibility regulations&apos;)
86+
</a>
87+
. If you&apos;re not happy with how we respond to your complaint, contact the{" "}
88+
<a href="https://www.equalityadvisoryservice.com/">Equality Advisory and Support Service (EASS)</a>.
89+
</p>
90+
91+
<h2>Technical information about the accessibility of Check and book an RSV vaccination</h2>
92+
<p>
93+
NHS England is committed to making this service accessible, in accordance with the{" "}
94+
<a href="https://www.legislation.gov.uk/uksi/2018/952/contents/made">
95+
Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018
96+
</a>
97+
.
98+
</p>
99+
<h3>Compliance status</h3>
100+
<p>
101+
This service is fully compliant with the{" "}
102+
<a href="https://www.legislation.gov.uk/uksi/2018/952/contents/made">
103+
Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018
104+
</a>
105+
.
106+
</p>
107+
<h2>Preparation of this accessibility statement</h2>
108+
<p>This statement was prepared on 26 September 2025. It was last reviewed on 26 September 2025.</p>
109+
<p>
110+
We continually test for accessibility needs. We&apos;re also committed to regular audits by independent
111+
specialist assessors.
112+
</p>
113+
<p>
114+
The NHS App was last audited by <a href="https://diginclusion.com">Dig Inclusion</a>
115+
</p>
116+
<p>iOS on 9 September 2025.</p>
117+
<p>Android on 9 September 2025.</p>
118+
<p>The browser version on 9 September 2025.</p>
119+
</section>
120+
</article>
261121
</MainContent>
262122
</>
263123
);

0 commit comments

Comments
 (0)