Accessibility statement for the Turing Scheme Portal

This accessibility statement applies to the portal website Turing Scheme Portal.

This portal has been developed by Capita plc. It is important that the portal is accessible and meets the legal requirement for businesses and organisations to make reasonable adjustments to provide accessible services and information. It is recommended that this website be used on a desktop device and a modern browser such as Chrome, Firefox, Safari, or Edge. We want as many people as possible to be able to use this portal. For example, that means you should be able to:

  • change colours, contrast levels and fonts by system or software
  • zoom in up to 300% without the text spilling off the screen
  • navigate most of the portal using just a keyboard, ensuring there are no keyboard traps
  • navigate most of the portal using speech recognition software
  • listen to most of the portal using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)

We have 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 portal is

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

  • some headings and labels are not descriptive enough
  • some aspects of our content expect previous knowledge of specialist terminology related to acquiring funding, however supplementary links to supporting website providing additional information have been provided
  • currently there is no confirmation of saved changes in the profile section, but these changes are saved
  • some of the information on this portal was created by a third party and we do not have the rights to change it and may not be fully accessible, due to this some information is not available in different formats such as accessible PDF, large print, easy read, audio recording or braille
  • some back links do not behave consistently as some use the browser back functionality rather than returning to the previous page in the sequence
  • navigating the change links on “Check your answers” page, expects the user to use the overview page to return to “Check your answers” page.
  • some buttons have additional behaviour that is not described by the button label
  • there are duplicated labels on some form pages where you add multiple items

What to do if you cannot access parts of this website

If you need information on this website in a different format, contact us.

Reporting accessibility problems with this portal

We are always looking to improve the accessibility of this portal. If you require information in a different format, find any problems not listed on this page, or think we are not meeting accessibility requirements, contact us.

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 are 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 Turing Scheme 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.1 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

  • When users are prompted to complete their profile there is no guidance on the ‘Profile’ page to indicate what level of information is required when editing their profile. This fails WCAG 2.1 success criterion 3.3.2 (Labels or Instructions).
  • On the ‘Change password’ page the descriptive text is not read out when the user is on the input field. This fails WCAG 2.1 success criterion 3.3.2 (Labels or Instructions).
  • There are some page titles that are generic and there are cases where the same page title is reused across multiple pages. This fails WCAG 2.1 success criterion 2.4.2 (Page Titled).
  • The back links on some pages use the browser back functionality rather than sequential page flow. When a user has completed editing their profile the back link navigates back to the edit profile page. This means some users may be confused by navigation. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships), 1.3.2 (Meaningful Sequence).
  • On the Mobility groups overview page, the “Mark as complete” button moves you to a new page and you can no longer access the pervious page. This is instructed on the page, but the button label does not explain the behaviour. This fails WCAG 2.1 success criterion 2.4.4 (Link Purpose (In Context)), 2.4.6 (Headings and Labels).
  • Some form field labels do not describe the question. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).
  • Some input fields of on the same page have the same label, despite having differing functionality. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships), 4.1.2 (Name, Role, Value), 3.3.2 (Labels or Instructions).
  • Some remove links do not describe the field(s) that are been removed. This fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships), 4.1.2 (Name, Role, Value), 3.3.2 (Labels or Instructions).
  • Some links open in a new tab without giving prior warning to the users about this behaviour. This fails WCAG 2.1 success criterion 3.2.5 (Change on Request).
  • There is an automatic sign out after 2 hours of no activity on the site, there is no prior warning. This fails WCAG 2.1 success criterion 2.2.1 (Timing adjustable), 2.2.2 (Pause, Stop, Hide).

Disproportionate burden

At this time, we have not made any disproportionate burden claims.

Content that is not within the scope of the accessibility regulations

PDFs and other documents. Some of our PDFs and Word documents are essential to providing our services. For example, we have PDFs that contain information on how users can access our services, and forms published as Word documents. We plan to either fix these or replace them with accessible HTML pages. Any new PDFs we publish will meet accessibility standards.

Completing the form on a mobile device

This has been tested on mobile and is fully responsive. Though we still recommend larger forms are completed on a desktop device.

Older browsers

Internet Explorer is not supported, and Microsoft has stated its intention to retire it, we have focused our efforts on making the accessible experience better in modern browsers.

What we are doing to improve accessibility

Accessibility checks are part of our development lifecycle and regular checks are made throughout in relation to Web Content Accessibility Guidelines version 2.1 AA standard and we investigate all issues raised. We will update this page when issues are found and fixed.

Preparation of this accessibility statement

This statement was prepared on 22 February 2022. It was last reviewed on 24 March 2022.

The portal was last tested on 24th March 2022. The testing is carried out internally on a weekly basis. The portal was tested based on a user’s ability to complete key journeys.