Accessibility statement

This accessibility statement applies to kidsonlinesafety.campaign.gov.uk.

This website is run by the Department for Education. 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 400% 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.

How accessible this website is

We know some parts of this website are not fully accessible:

  • Choose button is hidden until it receives focus
  • Start button focus is not clearly visible
  • Content blocks have the same ID
  • Cookies widget obscures focus at high zoom
  • Cookies widget button has unclear accessible name
  • Focus Order is Not Logical Using Android TalkBack
  • Unable to Interact with All User Interface Components Using Desktop Screen Reader
  • Semantic Markup Not Used Appropriately
  • Related Links Not Grouped Using Nav Element
  • Page Title is Not Descriptive
  • Tab Order is Not Logical
  • Heading Structure Incorrect
  • Rendering Issue Custom CSS Text Styling
  • Related Form Elements Not Grouped

Feedback and contact information

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

Email: customer.experience@education.gov.uk

We'll consider your request and get back to you in 5 working days.

Reporting accessibility problems with this website

We're always looking to improve the accessibility of this website. If you find any problems not listed on this page or think we're not meeting accessibility requirements, you can contact us using the following details:

Email: customer.experience@education.gov.uk

Enforcement procedure

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).

Technical information about this website's accessibility

The Department for Education is committed to making its websites accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

Compliance status

This website is partially compliant with the WCAG (Web Content Accessibility Guidelines) version 2.2 AA standard, due to the following non-compliances (and/or) the following exemptions.

Non-accessible content

The content is non-accessible for the following reason(s):

  • Choose button is hidden until it receives focus: When initially opening a question page (Quiz) there is no option for user to move forward. The ‘Choose’ button does not appear until receiving focus.

This could be confusing for users.

  • Start button focus is not clearly visible: The start button does not have a clear focus indicator which provides a clear perimeter to the element. Currently the focus style is just a size change when receiving keyboard and mouse focus.

This could impact keyboard only users who may be unaware of the size change and find it difficult to understand which element is currently in focus. (WCAG: 2.4.13)

  • Content blocks have the same ID: Many of the content blocks have the same ID.

This can cause accessibility issues when referencing ID’s within aria attributes.

  • Cookies widget obscures focus at high zoom: When viewing the service at high levels of zoom or at different viewports the focus can become obscured by the cookies widget.

Keyboard only users rely on keyboard focus indicators to navigate webpages and to orient themselves on the page. (WCAG: 2.4.12)

  • Cookies widget button has unclear accessible name: The accessible name for the cookies widget does not provide users with enough information to explain the function of the button. Currently the accessible name is provided via an aria-label which is ‘Open CMP Widget’. Many users would not understand the acronym for ‘CMP’ and therefore be unaware of what function the button servers. (WCAG: 4.1.2)
  • Focus Order is Not Logical Using Android TalkBack: When navigating the page using Android TalkBack, the focus order is not logical. It is expected that the navigation order of the page is logical and consistent.

It was found whilst navigating the site using Android TalkBack (a mobile screen reader) that when the user opened the Cookie Management Preferences overlay using the button present on all tested pages, then closed the dialog, no announcement was made as to where focus had returned to, and the user was still able to swipe through the Cookie Preferences options despite these no longer being visible on the page. (WCAG: 2.4.3)

  • Unable to Interact with All User Interface Components Using Desktop Screen Reader: When tabbing the page using a desktop screen reader, the user is unable to tab to all of the elements within the page. It is expected that all page functionality is available using the keyboard, unless the functionality cannot be accomplished in any known way using only the keyboard (e.g. freehand drawing).

Globally, it was observed that when navigating the site using a desktop screen reader (NVDA), it was not possible to navigate to, or interact with, the Cookies overlay which was displayed on first page load. (WCAG: 2.1.1)

  • Semantic Markup Not Used Appropriately: When viewing the code behind the page semantic markup is not used appropriately for headings. It is expected that semantic markup is used appropriately and to designate headings, lists, emphasised or special text etc.

It was observed on the Info, Report It, and Support pages that there were headings present which were styled visually as headings but were not marked up semantically using. It is expected that headings which define sections of page content are marked up semantically in order to allow screen reader users to navigate quickly to different areas of the page and understand the overall page structure. (WCAG: 1.3.1)

  • Related Links Not Grouped Using Nav Element: When reviewing the code behind the page, it has been identified that related links are not grouped using a semantic "nav" element. It is expected that links which are visually presented as a group are also programmatically grouped to convey their relationship to assistive technologies.

When viewing the “on this page” component observed across multiple pages, it was found that the links are not contained within a navigation landmark. Some screen reader users navigate using landmarks and may find it useful to quickly navigate to the navigation regions on the page. (WCAG: 1.3.1)

  • Page Title is Not Descriptive: When viewing the page, the page title is not descriptive. It is expected that the page has a descriptive and informative page title.

It has been noted the ‘Home’ page title announces ‘Help your child stay safe online - Kids Online Safety %’ which may confuse screen reader users as it alludes to a process with the percentage character. It has also been observed the ‘Quiz’ page does not update its page titles when a user navigates the quiz or the ‘Quiz – Outcome’ section. It is expected page titles change dynamically so screen reader users can be informed of the change of context (WCAG: 2.4.2)

  • Tab Order is Not Logical: When tabbing the page, the tab order is not logical. It is expected that the navigation order of the page is logical and consistent.

It was found when navigating the site using only a keyboard, that after the user answered a question on the Quiz Question1 and Quiz Question 5 pages that the tab order of the ‘Next’ and ‘Show Question’ buttons did not match the visually presented order, with the ‘Show Question’ button receiving keyboard focus first. (WCAG: 2.4.3)

  • Heading Structure Incorrect: When viewing the code behind the page, the heading hierarchy is incorrectly structured. It is expected that the headings are correctly nested, e.g. a 'h2' heading is nested in a 'h1' heading. If a page has a proper heading structure, this may be considered a sufficient technique instead of a 'Skip to main content' CTA. Skipped heading levels can result in screen reader users missing content. (WCAG: 2.4.1)
  • Rendering Issue Custom CSS Text Styling: When applying a custom CSS text styling, rendering issues are observed. It is expected that text is displayed without loss of functionality or content.

When CSS is applied, line height (line spacing) to at least 1.5 times the font size. Spacing following paragraphs to at least 2 times the font size. Letter spacing (tracking) to at least 0.12 times the font size and word spacing to at least 0.16 times the font size. (WCAG: 1.4.12)

  • Related Form Elements Not Grouped: When viewing the code behind the page related form elements are not grouped with fieldset/legend. It is expected that related form elements are grouped by a fieldset/legend, e.g. the user's home address and work address fields are grouped separately. (WCAG: 1.3.1)

Preparation of this accessibility statement

This statement was prepared on 22 May 2026.

This website was last tested on 13 February 2026. The test was carried out by Zoonou. We used this approach to deciding on a sample of pages to test, External Audit.

Accessibility statement version: 1