Accessibility Statement

This website is run by Flipside Group. 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:

·   some content across the site lacks contrast which may make content difficult to read

·   when tabbing the page, a clear and consistent visible focus indicator is not always present

·   the focus order is not always logical when navigating on both desktop and mobile environments

·   some page content may not be contained within a landmark element

·   the heading structure is not always correct

·   some videos do not contain audio descriptions

·   PDFs may not be fully accessible to assistive technology and keyboard-only navigation.

 

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

Flipside Group is committed to making its website 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 Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed below.

 

Non-accessible content

The content listed below is non-accessible for the following reasons.

Non-compliance with the accessibility regulations

Some informative images do not have an appropriate text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).

 

Buttons do not have appropriate labels. Buttons without labels do not provide information about their functionality to screen reader users. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).

 

Some decorative elements are announced when navigating with a mobile screen reader, which can create unnecessary noise for users. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).

 

Some images and graphs/charts in PDFs do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).

Some videos include on-screen text that conveys important information and context which is not available through the audio. This content is not spoken aloud and is not included within the captions or transcripts, making it inaccessible to users who rely on audio descriptions. This fails WCAG 2.2 success criterion 1.2.5 (audio description (pre-recorded)).

Related form elements within the Gambling harms assessment are not grouped using a fieldset and legend. Assistive technologies may not accurately convey the relationship and context of these grouped form controls to users. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).

 

Regions of the pages are not identified with appropriate unique landmarks. This may be confusing to assistive technology users who navigate using landmarks. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).

 

Semantic markup has not been used appropriately for lists within the Cookie Notice. The intended relationship between this content may not be conveyed to assistive technology users. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).

 

Related breadcrumb links are not contained with a navigation element. As a result, the relationship between these links is not communicated to users of assistive technologies. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).

 

A table on the Cookie Policy page is incorrectly formed, with table header cells not marked up as such. Screen reader users may have difficulty navigating these tables. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).

 

Tables within PDFs have irregular table rows and header cells which are not assigned to corresponding data cells. Some content such as images are incorrectly nested within table tags. This fails WCAG 2.2 success criterion 1.3.1 (info and relationships).

 

For some input fields, such as ‘Postcode’, the autocomplete attribute is not present. This may require the user to manually fill these inputs. This fails WCAG 2.2 success criterion 1.3.5 (identify input purpose).

 

Links within the Publication Library page are indicated by colour alone. Users who have difficulty distinguishing colours may be unable to identify link text. This fails WCAG 2.2 success criterion 1.4.1 (use of colour).

 

Information within PDFs are communicated only by colour. This may be difficult to understand for users with visual impairments or colour blindness. This fails WCAG 2.2 success criterion 1.4.1 (use of colour).

 

Text throughout the website lacks contrast against its background. People with low vision may have difficulty reading text that does not contrast with its background. This fails WCAG 2.2 success criterion 1.4.3 (contrast (minimum)).

 

Text such as headings and links does not meet sufficient contrast requirements against the page background within PDFs. This fails WCAG 2.2 success criterion 1.4.3 (contrast (minimum)).

 

Zooming the page to 400% with a browser width of 1280px results in content not being available in full, making it difficult to read. This fails WCAG 2.2 success criterion 1.4.10 (reflow).

 

Some user interface components may not meet the contrast minimum of 3.5:1. This may make it difficult for users to distinguish interactive elements. This fails WCAG 2.2 success criterion 1.4.11 (non-text contrast).

 

Content within the Service Finder pages is cut off when custom Cascading Style Sheets (CSS) text spacing is applied. This can make some text difficult to read for users who require increased spacing between lines, words, or letters. This fails WCAG 2.2 success criterion 1.4.12 (text spacing).

 

A correctly formed heading structure is not present on the Search Results page to facilitate navigation, with a skipped heading level present. This fails WCAG 2.2 success criterion 2.4.1 (bypass blocks). 

 

PDFs do not have a Level 1 Heading at the start of the document and may contain missed heading levels within their heading structure. Bookmarks are also not set within PDFs based on the headings in the document. This fails WCAG 2.2 success criterion 2.4.1 (bypass blocks). 

 

Some page titles are repeated across multiple web pages, and several page titles are not descriptive, which may cause navigation issues between tabs. This fails WCAG 2.2 success criterion 2.4.2 (page titled).

 

The focus order is not always logical when navigating with a keyboard, and with desktop and mobile screen readers enabled. This may result in keyboard and/or screen reader users becoming disoriented. This fails WCAG 2.2 success criterion 2.4.3 (focus order).

 

Multiple instances of duplicated link text are present such as ‘Watch video’ and ‘Find support providers’, which do not sufficiently inform screen reader users where they will be navigated to upon interaction with the links. This fails WCAG 2.2 success criterion 2.4.4 (link purpose (in context)).

 

Links within PDFs have no alternative text and may be announced incorrectly by screen readers. This fails WCAG 2.2 success criterion 2.4.4 (link purpose (in context)).

 

When tabbing the page, a consistent visible focus indicator is not always present. This can make it difficult for keyboard only users to keep track of the elements currently in focus. This fails WCAG 2.2 success criterion 2.4.7 (focus visible).

 

Some accessible names may differ from the visual name of user interface components. This may result in users of speech recognition software being unable to interact with these inputs. This fails WCAG 2.2 success criterion 2.5.3 (label in name).

 

Within the Live Chat modal, elements use unsupported ARIA attributes. Using ARIA attributes in roles where they are not allowed can interfere with the accessibility of the web page. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).

 

Nested interactive controls are present within the Gambling Harms Assessment Landing page. Focusable elements with an interactive control are not announced by screen readers and create an empty tab stop. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).

 

PDF Metadata such as title, language and the PDF/UA Identifier are not set on most PDFs. This may impact how assistive technology communicates the PDF topic and information. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).

 

Text is contained within an Artifact and white space is also tagged. This may result in screen readers missing this content or announcing it incorrectly. This fails WCAG 2.2 success criterion 4.1.2 (name, role, value).

 

Preparation of this accessibility statement

This statement was prepared on 29/01/2026. It was last reviewed on 29/01/2026.

This website was last tested on 28/01/2026. The test was carried out by Zoonou.

Zoonou used WCAG-EM to define the pages tested and test approach.