This accessibility statement applies to the Turing Scheme website, application portal and reporting portal.
The website, application portal and reporting portal are run by the Turing Scheme delivery partner, a consortium between the British Council and Ecorys UK. We are committed to making our online platforms accessible to all and aim to meet Web Content Accessibility Guidelines (WCAG) 2.1 level AA.
We want as many people as possible to be able to use this website. You can use the One Click Accessibility plugin to make changes to the website and make it more accessible for you. You can find the One Click Accessibility plugin at the top right-hand corner of the page.
On this website, you should be able to:
- change colours, contrast levels and fonts
- underline links
- increase text size and 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 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 website is
We know some parts of this website are not fully accessible:
- Some documents are in PDF format and are not fully accessible to screen reader software but measures have been taken to ensure these documents are as accessible as possible
How accessible the application portal is
We know that some parts of the application portal are not fully accessible:
- You cannot access some sections of the application form using just a keyboard
How accessible the reporting portal is
We know that some parts of the reporting portal are not fully accessible:
- You cannot access some of the content using just a screen reader
- You cannot access some of the content using just a keyboard
Reporting accessibility issues
If you are experiencing any issues using this website or the application or reporting portals, think we are not meeting the accessibility requirement or need information in a different format (e.g. PDF or large print), please contact us via email.
Technical information about accessibility
The Turing Scheme delivery partner is committed to making its website, application portal and reporting portal accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
The website, application portal and reporting portal are partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances and exemptions listed below.
The content below is non-accessible for the following reasons:
Non-compliance with the accessibility regulations
- Some documents are in less accessible PDF formats. Non HTML documents published on or after 23 September 2018 must have an accessible format.
- Some content of the application form is not accessible with keyboard use only. This fails WCAG success criterion Level A (2.1.1 Keyboard).
- Some areas of the portal do not have Accessible Rich Internet Application (ARIA) roles needed to communicate relationships to screen readers. This fails WCAG 2.1 success criterion 1.3.1 (Info and relationships).
- On some pages, the main landmark is not defined for screen readers. This fails WCAG success criterion 2.4.1 (Bypass Blocks).
- Some pages do not have their heading text tagged for screen readers. This fails WCAG success criterion 1.3.1 (Info and relationships).
- Some heading-texts are not tagged under the heading structure for screen reader users. This fails WCAG success criterion 1.3.1 (Info and relationships).
- Screen reader focus does not automatically move in “Grant not found” dialog after selecting “Project Search” button without adding the information in “Grant agreement unique reference number (URN)” edit-field. This fails WCAG success criterion Level A (2.4.3 Focus Order).
- Incorrect role is implemented for “Introduction, Select Grant Application, Project Overview” elements. This fails WCAG success criterion Level A (4.1.2 Name, Role, Value).
- Screen reader focus does not automatically move to the updated content which appears on activating “Previous period and Next period” buttons. This fails WCAG success criterion Level A (2.4.3 Focus Order).
- Screen reader does not announce the updated link text of “Select placement” link. This fails WCAG success criterion Level A (4.1.2 Name, Role, Value).
- Screen reader does not identify the disabled state of “Current placement” link. This fails WCAG success criterion Level A (4.1.2 Name, Role, Value).
- Icon “Calendar” not triggerable through keyboard as the Start date ‘calendar’ button icon does not receive tab focus. This fails WCAG success criterion Level A (2.1.1 Keyboard).
- Screen reader does not automatically announce the current word count in the edit field. This fails WCAG success criterion Level A (1.3.1 Info and Relationships).
- The visual graphic icons associated with navigation buttons are not focusable by any means. This fails WCAG success criterion Level AA (2.1.1 Keyboard) (1.1.1 Non-text Content).
- Log on page > Purpose of the input form fields collecting user’s personal information is not appropriately defined. This fails WCAG success criterion Level AA (1.3.5 Identify Input Purpose).
It is not possible for users to change text size using the One Click plugin without some of the content overlapping.
Content that’s not within the scope of accessibility regulations
Human verification such as CAPTCHA may be inaccessible to those who cannot use a computer mouse and some assistive technology.
What we are doing to improve accessibility
We will aim to remediate all non-compliances by March 2022.
How we test the website, application portal and reporting portal
Both online platforms are tested for compliance with the Web Content Accessibility Guidelines V2.1 level A and level AA. We use both automated testing tools along with internal and external manual audits.
Preparation of this accessibility statement
This statement was last updated on 9 September 2021.
This website was last tested on 17 January 2021.
The application portal was last tested on 10 February 2021.
The reporting portal was last tested on 5 August 2021.