This accessibility statement applies to content published on the Funding Service domain.
This website is run by UK Research and Innovation (UKRI). 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 300% without the text spilling off the screen
- navigate most of the service using just a keyboard
- navigate most of the service using speech recognition software
- listen to most of the service using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver).
We’ve also made the service 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. For example:
- some page elements are not accessible to all users
- some tables do not have row headings
- some page titles are not unique or suitable descriptive.
Feedback and contact information
If you need information from this service in a different format like accessible PDF, large print, easy read, audio recording or braille:
- email: support@funding-service.ukri.org
- telephone: 01793 265 810.
In your message, include:
- the web address (URL) of the content
- your email address and name
- the format you need. For example, plain text, braille, British Sign Language, large print or audio CD.
We’ll consider your request and get back to you in 2 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, contact support@funding-service.ukri.org.
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
UKRI is committed to making this service accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Compliance status
This service is partially compliant with the Web Content Accessibility Guidelines version 2.1 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 the accessibility regulations
Perceivable
Some information is being shared through visual presentation only. This means some fields and tables do not properly convey the structure of content or its relationship to other elements on the page. This fails WCAG 2.1 success criteria 1.3.1 (info and relationships).
Some page elements do not meet the minimum colour contrast requirements. This means some text may not be easy to read due to the colour of the background. This fails WCAG 2.1 success criteria 1.4.3 (contrast (minimum)).
There is loss of some content or functionality when text spacing is overridden. This means some of the text may not be easy to read due to the spacing between lines, paragraphs, letters and words. This fails WCAG 2.1 success criteria 1.4.12 (text spacing).
Operable
Some page elements are not accessible to keyboard commands. This means that when using a keyboard or assistive technologies, it may not be possible to complete the service. This fails WCAG 2.1 success criteria 2.1.1 (keyboard).
Some users are not able to turn off, adjust or extend the time in which inactivity will result in a loss of data. This means that where there is a time limit set in the service, there is no option to turn-off, delay or extend the length of time. This fails WCAG 2.1 success criteria 2.2.1 (timing adjustable).
Some page titles do not uniquely describe or introduce the page content. This means that page titles do not clearly describe the topic or purpose of the page. This fails WCAG 2.1 success criteria 2.4.2 (page titled).
Some page elements cannot be accessed by all users. This means that when using a keyboard or assistive technologies it may not be possible to navigate the page in a way that makes sense. This fails WCAG 2.1 success criteria 2.4.3 (focus order).
Some page headings are not descriptive enough. This means that headings and labels do not clearly describe what their topic or purpose is. This fails WCAG 2.1 success criteria 2.4.6 (headings and labels).
Some visible labels do not match the hidden accessible names. This means assistive technologies may not be able to read it correctly. This fails WCAG 2.1 success criteria 2.5.3 (label in name).
Understandable
Some user actions trigger an unexpected response from page features, initiating a change in focus and context. This fails WCAG 2.1 success criteria 3.2.1 (on focus).
Some user actions cause an unexpected change in the setting of a user interface component. This fails WCAG 2.1 success criteria 3.2.2 (on input).
Some error messages do not adequately describe what went wrong or how to fix it. This fails WCAG 2.1 success criteria 3.3.3 (error suggestion).
Robust
Some page elements reference duplicate ID values. This means that the page may not work reliably for all users. This fails WCAG 2.1 success criteria 4.1.1 (parsing).
Some form controls are not detectable by screen reader software. This fails WCAG 2.1 success criteria 4.1.2 (name, role, value).
Some error messages are displayed in a way that may not be picked up by assistive technology. This fails WCAG 2.1 success criteria 4.1.3 (status messages).
What we’re doing to improve accessibility
We’re currently assessing how best to fix the non-compliance issues. We believe that rather than tackling issues individually, a wider review and change to our approach would offer a longer term solution that’s more cost effective to the public.
We will complete our assessment and update this statement again with actions and timelines no later than 31 March 2023.
Preparation of this accessibility statement
This statement was prepared on 30 June 2020. It was last reviewed on 7 December 2021.
This service was last tested on 24 September 2021. The test was carried out by the Digital Accessibility Centre (DAC).
To give a more accurate review of the service, the DAC team used a combination of automated and manual testing. The manual testing was by a team of user testers with differing disabilities using a range of adaptive technologies.
As we continue to develop the service and its content, we will re-audit and test the service for accessibility on a regular basis.
Last updated: 16 January 2023