Skip to content

Edits to accessibility statement page #669

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
frankieroberto merged 2 commits into from
Feb 18, 2026
Merged

Edits to accessibility statement page #669

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fc11290
Update accessibility-statement.html
Anna-Sutton Feb 18, 2026
3ed1367
Added a space in accessibility-statement.html
Anna-Sutton Feb 18, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions app/views/accessibility-statement.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,14 +35,14 @@ <h2>Give feedback and report accessibility problems</h2>


<h2>Enforcement procedure</h2>
<p>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’).</p>
<p>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').</p>
<p>If you’re not happy with how we respond to your complaint, <a href="https://www.equalityadvisoryservice.com/">contact the Equality Advisory and Support Service (EASS)</a>.</p>

<h2>Technical information about this website’s accessibility</h2>
<p>NHS England is committed to making this service accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.</p>

<h2>Compliance status</h2>
<p>This service is partially compliant with the <a href="https://www.w3.org/TR/WCAG22/">Web Content Accessibility Guidelines version 2.2 </a>AA standard, due to the non-compliances listed below.</p>
<p>This service is partially compliant with the <a href="https://www.w3.org/TR/WCAG22/">Web Content Accessibility Guidelines version 2.2</a> AA standard, due to the non-compliances listed below.</p>


<h2>Non-accessible content</h2>
Expand All @@ -64,7 +64,7 @@ <h4>Record a vaccination section</h4>
<li>On the Find a patient page, Aria labels are used when not needed. (4.1.2 Name, Role, Value) </li>
<li>On the Find a patient page, when clicking on search, results appear at the bottom of the page. This is not announced to screen readers and focus moves to the top of the page. (1.3.2 Meaningful Sequence) </li>
<li>On the Patient details page, there are empty fieldsets in the tables which may cause confusion. (1.3.1 Info and Relationships)  </li>
<li>On the Patient details page, the 'Continue' button appears before the vaccination history. Screen reader users many never get to this content. (1.3.2 Meaningful sequence) </li>
<li>On the Patient details page, the 'Continue' button appears before the vaccination history. Screen reader users may never get to this content. (1.3.2 Meaningful sequence) </li>
<li>On the Assess and Vaccinate pages, the date picker does not work well with keyboard navigation and screen readers. (1.3.1 Info and Relationships)  </li>
<li>On the Vaccinate page, disabled fields are used for dose and expiry date which may cause confusion for some users. (1.3.3 Sensory Characteristics) </li>
<li>On the Check and confirm page, all the content is contained within a fieldset. This can create extra confusion for screen reader users. (1.3.1 Info and Relationships) </li>
Expand Down