This accessibility statement explains how accessible the UKRI Funding Service application is and how to report accessibility problems with it.
This service is not part of the wider GOV.UK website. There is a separate accessibility statement for the main GOV.UK website.
This page only contains information about UKRI Funding Service.
Using this service
UKRI Funding Service facilitates applications from universities, research organisations, industry and interested individuals for grants and funding, for research and innovation initiatives within the UK.
This service is part of ukri.org and is run by UKRI. One of its aims is to make sure as many people who need to use it can do so.
It has been designed so users can:
- change colours, contrast levels and fonts
- 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.
If you have a disability, AbilityNet has help and advice to make your device easier to use.
This website has been tested with a wide range of browser software and is compatible with the latest versions of Internet Explorer, Google Chrome, Mozilla Firefox and Mac Safari.
This website has also been tested on mobile platforms including Google Android and Apple iOS.
- you have the latest version of Java installed on your computer, or device
- that it is enabled for use.
Refer to your web browser’s help file to find out how to do this.
How accessible is this application?
Following a comprehensive test carried out by the Digital Accessibility Centre (DAC) against Web Content Accessibility Guidelines version 2.1 AA standard, a number of defects were identified. As we go live, UKRI are confident all the amendments and changes that needed to be made to meet the non-compliant aspects of the service (listed below) have been completed. It is therefore the contention of UKRI that this service is compliant. However, we must stress that this is subject to confirmation upon a re-test of the service.
At the time of publication, a re-test was in the process of being scheduled. Once we have the results, we will update this statement accordingly.
Reporting accessibility problems with this website
We are always looking to improve the accessibility of this website. If you find any problems, or you think we are not meeting accessibility requirements, contact email@example.com
We will review your request and aim to get back to you in 2 working days.
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).
We can provide you with information and advice on UKRI Opportunities. We also provide help and technical support on using the UKRI Funding Service. Please respect our staff and funding service partners at all times. We will not tolerate abuse in any form, written or spoken.
We provide personalised assistance to people who need help using our online funding service.
Please contact us well before you need to meet any deadlines, to make sure we have enough time to tailor a solution for you.
Call Call +44 (0) 1793 265810 to speak to the UKRI Funding Service Helpdesk. Our lines are open from 9am to 4.30pm, Monday to Friday (excluding bank holidays).
Send your question or query to firstname.lastname@example.org and we’ll get back to you as soon as possible.
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.
Following an accessibility audit carried out by the Digital Accessibility Centre (DAC) the areas listed under ‘Non-accessible content’ were identified as inaccessible. Since that report, we believe we have fixed these issues but this needs to be confirmed by a re-test with DAC.
The DAC audit revealed the following areas as not meeting accessibility the Web Content Accessibility Guidelines version 2.1 AA standards:
- Error Identification 3.3.1 There was no mechanism in place for users to identify when they had made an error.
- Component Purpose 2.4.3 Focus Order, 4.1.2 – Name, Role, Value – Focusable components did not receive focus in an order that preserved meaning and operability.
- Link Purpose 2.4.4 Link Purpose (In Context), 2.4.9 Link Purpose (Link Only) – The purpose of links could not be determined from the link text together with the programmatically determined link context (i.e. text in the same paragraph, list, or table cell as the link or in a table header cell that is associated with the table cell that contains the link.
- Status Messages 4.1.3 Status Messages – There were status messages that were not relayed to screen reader users.
- Landmarks 4.1.1 Parsing Landmarks were not implemented according to specification.
- Form Groups 1.3.1 Info and Relationships, 3.3.2 Labels or Instructions, 2.4.6 Headings and Labels – Semantic grouping was not provided for related form controls.
- Regions 1.3.1 Info and Relationships, 1.3.2 Meaningful Sequence – Relationships on the page were indicated by the visual placement of content and were not programmatically determinable.
- Non-descriptive Labels 2.4.6 Headings and Labels – Labels were implemented that did not clearly describe the topic or purpose.
- Page Purpose 2.4.2 Page Titled, 2.4.6 Headings and Labels – The purpose of the page could not be identified by the page heading (h1) and page title.
How we tested this service
The service was tested on 15 June 2020 and was checked for compliance with WCAG 2.1 AA by DAC.
As we went to publication we are waiting a re-test with DAC to confirm the above issues are fixed, which we anticipate happening in due course, to make the service fully compliant with WCAG 2.1 AA.
This page was prepared on 3 August 2020. It was last updated 1 July 2021.
Last updated: 1 July 2021