Accessibility Statement

Home
About NPSA
Accessibility Statement

Accessibility statement for NPSA Public Website

This accessibility statement applies to: https://www.npsa.gov.uk/

This website is run by the National Protective Security Authority (NPSA).

We want as many people as possible to be able to use this website. For example, that means you should be able to:

change colours, contrast levels and fonts
zoom in up to 300% without the text spilling off the screen
navigate most of the website using just a keyboard
navigate most of the website using speech recognition software
listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We’ve also made the website text as simple as possible to understand.

AbilityNet has advice on making your device easier to use if you have a disability.

Non-compliance with the accessibility regulations

Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (Non-Text Content).

Some decorative images have an alternative attribute when a null alternative is expected. This may mean that some screen readers focus on decorative images. This fails WCAG 2.1 success criterion 1.1.1 (Non-Text Content).

Some images within Word documents and PDF documents lack a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.1 success criterion 1.1.1 (Non-Text Content).

Some videos on the website may not have synchronised captions that can be enabled. This fails WCAG 2.1 success criterion 1.2.2 (Captions).

Some videos on the website may lack a text-based transcript to accompany the video. This fails WCAG 2.1 success criterion 1.2.3 (Audio Description or Media Alternative (Pre-Recorded)).

Videos on the website lack a separate audio description track describing the contents of the video. This fails WCAG 2.1 success criterion 1.2.5 (Audio Description (Pre-Recorded)).

Some pages contain headings within a heading, this may cause unexpected behaviour when navigating using headings with a screen reader. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).

Some PDF documents are not tagged, which may result in the content being inaccessible to screen readers. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).

Some pages may contain empty headings, these headings may be focusable by screen readers and contain no content. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).

Some related groups of links are not grouped together using the <nav> element. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).

Some Word documents contain non-inline graphics or objects that do not have a text alternative, so screen readers can’t access this information. This fails WCAG 2.1 success criterion 1.3.2 (Meaningful Sequence).

When zooming text only, some content become truncated and inaccessible. This includes the navigation menu, as well as sections of content on selected pages. This fails WCAG 2.1 success criterion 1.4.4 (Resize Text).

Some content may be implemented as images of text, which may be inaccessible to some users. This fails WCAG 2.1 success criterion 1.4.5 (Images of Text).

Some pages may contain an animation that lacks the ability to pause, stop, or hide the content on the page. Some users may find this content distracting. This fails WCAG 2.1 success criterion 2.2.2 (Pause, Stop, Hide).

Some PDF documents may lack an appropriate title identifying the content of the PDF to screen reader users. This fails WCAG 2.1 success criterion 2.4.2 (Page Titled).

Some headings and labels are not representative of the content present, which may be confusing for some screen reader users. This fails WCAG 2.1 success criterion 2.4.6 (Headings and Labels).

Some PDF documents may not have defined the language of the file. This may result in some content being pronounced incorrectly. This fails WCAG 2.1 success criterion 3.1.1 (Language of Page).

Not all elements can be interacted with using all screen readers. Some drop-downs on the All Guidance Articles page are not accessible via NVDA and Windows Narrator. This fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value).

Some PDF documents do not contain XMP metadata, which may result in some context being lost for users who rely on screen readers. This fails WCAG 2.1 success criterion 4.1.2 (Name, Role, Value).

Some tables require two-dimensional scrolling on mobile devices, which can make it difficult for users to understand the relationship between the header and data cells. This fails WCAG success criterion 1.4.10 (Reflow).

Some form labels do not reference valid ID attributes, which may prevent screen reader users from understanding the purpose of form fields. This fails success criterion 1.3.1 (Info and Relationships).

Some video embed content uses duplicate ID attributes, which can cause confusion for assistive technologies that rely on unique element identifiers. This fails success criterion 4.1.1 (Parsing).

Please refer to our roadmap for when these issues will be fixed.

PDFs

NPSA's websites contain approximately 2,000 PDF documents.

We are going through an extensive review of all published content, including PDFs As part of that process, we will, wherever possible, create HTML pages to either exist alongside or replace the PDF documents; and ensure those PDFs that remain meet current guidelines. Wherever we are able to remove PDF versions of our guidance, we will.

We estimate that this process will take around 2 years to complete.

All PDFs uploaded onto our site from April 2023 meet WCAG 2.1 AA standards.

If you require a particular piece of guidance in a more accessible format, please contact us via our enquiries form selecting Accessibility as the topic.

Interactive tools and transactions

Some of our interactive forms are difficult to navigate using a keyboard. For example, because some form controls are missing a ‘label’ tag.

Our forms are built and hosted through third party software and ‘skinned’ to look like our website.

We are aware that the following tools are not accessible:

Data Centre Security Risk animation
We have assessed the cost of fixing this animation, but we believe that doing so would be a disproportionate burden, as we provide the content in an accessible format.

Protecting your assets tool
We are unable to fix this tool due to the way it has been built. We therefore will be retiring it in 2026.

Passport to Good Security
We are aware that the functionality at the bottom of this section of the website isn’t accessible. We have assessed the cost of fixing the issues associated with it, and believe that doing so would be a disproportionate burden. We are planning to create this content in the form of a HTML webpage by 2026.

Supply Chain Guidance tool
We have assessed the cost of fixing this animation, but we believe that doing so would be a disproportionate burden, as we provide the content in an accessible format.

Security Minded Approach game
We are unable to fix this tool due to the way it has been built. We therefore will be retiring it from the website in 2026.

PDFs and other documents

Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs with information on how users can access our services, and forms published as Word documents.

The accessibility regulations do not require us to fix PDFs or other documents published before 23 September 2018 if they’re not essential to providing our services.

See the above section "PDFs" under Disproportionate Burden for an outline of how we plan to tackle this issue.

Did you find this page useful? Yes No

Accessibility Statement