Get a quote

Accessibility Statement for RestoreWeb

Accessibility Statement for RestoreWeb

Accessibility Statement for RestoreWeb

This accessibility statement applies to the RestoreWeb platform.

This platform is run by Restore PLC and is designed to be used by as many people as possible. That means you should be able to:

  • change colours, contrast levels and fonts using browser or device settings
  • zoom in up to 400% without loss of content or the text spilling off the screen
  • navigate most of the platform using a keyboard or speech recognition software
  • listen to most of the platform using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

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

How accessible this platform is

We know some parts of the platform are not fully accessible due to:

  • Mobile responsivity and browser zoom issues
  • Missing or incorrect keyboard focus orders
  • Keyboard focus indicator visibility and contrast issues
  • Incorrect html semantics and labels in data tables
Feedback and contact information

If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: oneilsupport@restore.co.uk

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

Email: oneilsupport@restore.co.uk

call 01684 855089

We’ll consider your request and get back to you within 14 days.

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 platform’s accessibility

Restore PLC is committed to making its platform accessible, in accordance with the Public Sector Bodies (website and Mobile Applications)(No. 2) Accessibility Regulations 2018.

Compliance status

This platform has been tested against the Web Content Accessibility (WCAG) 2.2 AA standards.

This platform is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances and exemptions listed below.

Non-accessible content

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

Non-compliance with accessibility regulations
Colour contrast

The colour contrast of text against a coloured background does not meet the ratio of 4.5.1 across the platform. This fails WCAG 2.2 success criterion 1.4.3 (Contrast minimum).

Keyboard accessible

There are some interactive elements on the platform that are not accessible for keyboard users. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard Level A).

Missing keyboard focus

The Keyboard focus indicator is missing on some interactive elements. This fails WCAG 2.2 success criterion 2.4.7 (Focus Visible).

Keyboard focus order

The keyboard focus order has some inconsistencies where the focus order changes direction or causes the user to restart the navigate from the top of the page.

This fails WCAG 2.2 success criterion 3.2.3 (Consistent Navigation).

Associated link text

Some link text does not clearly describe to users what will happen if the link is clicked. This fails WCAG 2.2 success criterion 2.4.4 (Link Purpose in Context).

Zoom to 400%

Some content, including large tables and form elements, does not reflow correctly when the browser is resized to 400% zoom. This fails WCAG 2.2 success criterion 1.4.10 (Reflow).

Form labels

The input boxes on the platform are not all correctly labelled meaning the purpose and functionality of the elements could be confusing to assistive technology users. This fails WCAG 2.2 success criteria:

1.1.1 (Non Text Content) Level A

1.3.1 (Info and Relationships) Level A

2.4.6 (Headings and Labels) Level AA

3.3.2 (Labels or Instructions) Level A

Incorrect table HTML semantics and Labels

Some data tables include header cells; however, the appropriate scope attributes are not consistently applied to ensure that header relationships are programmatically associated with corresponding data cells meaning some table header labels are currently hidden from screen readers due to aria-hidden being applied. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).

Changes to content

A JavaScript jump menu is present, meaning when a keyboard user browses a dropdown the page content will change automatically. This fails WCAG 2.2 success criterion;
2.1.1 (Keyboard Level A)
3.2.2 (On Input)

Abbreviation

Some abbreviations are read out phonetically by screen readers, which can cause confusion. This fails WCAG 2.2 success criteria:
3.1.4 (Abbreviations Level AAA)
3.2.2 (On Input)

Content that’s not within the scope of the accessibility regulations

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.

What we’re doing to improve accessibility

Work continues internally and with agencies to fix content that fails to meet the Web Content Accessibility Guidelines version 2.2 AA standard.
The next release is currently scheduled no later than the 31st July 2026.

Preparation of this Accessibility Statement

This statement was prepared on 16 February 2026. It was last reviewed on 20 February 2026.

The platform was last tested on 15 February 2026 against the WCAG 2.2 AA standard.

The test was carried out by Invuse. The most viewed pages and key user journeys were tested using automated and manual testing tools using Google Chrome, Microsoft Edge and Apple Safari.

You can read the full accessibility test report on request.

 

Related Services