Skip to main content

We’ve updated our privacy policy including changes to how we transfer and process your data. Find out more HERE.

Accessibility

Part of our commitment to you is to make sure everyone can access this website and the information it contains easily.

We know we can always do more.

Contact us if you’re struggling to access part of this website or to tell us about your experience.

Your ease of accessibility matters. Find out about more about what we’re doing and how to access this website using alternative methods below.

Accessibility statement for Anthony Nolan

This accessibility statement applies to the website found at https://www.anthonynolan.org/

This website is run by Anthony Nolan. 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 400% 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)

How accessible this website is

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

  • Our videos do not have an alternative format, such as a transcript or audio description. People using screen reader software may not be able to access all the visual information.
  • All of our videos have captions but they may not always be accurate or have punctuation, making them harder to read and understand for people with hearing impairments.
  • Our pages and forms are generally well structured. There are a small number of pages where headings are not applied properly, inputs do not have text label elements, links are not grouped, iframe elements do not have titles, and a small number of pages do not have descriptive titles. This may make the structure of some pages harder to understand for people who use screen reader software.
  • On the first page of the donor application form the pre-screener questions are radio buttons. If “No” is accidentally selected, keyboard-only users are informed that they are not eligible without a chance to change their answer. Users can alter their responses by refreshing the page.
  • On a small number of pages, the current location in the secondary navigation is only distinguished from the surrounding text by colour, which may make it hard for some people to distinguish from plain text.
  • When a new page loads in the donor application form pages, keyboard focus may not be at the top of the page.
  • A limited number of controls do not receive keyboard focus. On the Donor application form pages, progress bar elements receive keyboard focus when they should not. It is not always possible to see keyboard focus on every element.
  • On pages with forms errors are not automatically conveyed to screen reader software users in forms mode. By entering reading mode, however, error messages are discoverable.
  • There are a small number of components that do not provide sufficient contrast, which may make some components harder to read for people with low vision.
  • In a text input form the purpose of each input field (which collects information about the user) can be understood by assistive technologies. Some input elements are missing the necessary attributes for this to happen.

Feedback and contact information

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 us.

Technical information about this website’s accessibility

Anthony Nolan is committed to making its website accessible.

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:

  • Our videos do not have an alternative format, such as a transcript or audio description. People using screen reader software may not be able to access all the visual information. This fails WCAG 2.1 success criterion 1.2.3 (Audio Description or Media Alternative (Pre-recorded)).
  • We plan to provide alternative formats for all videos by August 2022. When we publish new content, we’ll make sure our multimedia content is available in another format.
  • Our videos have captions, they are not always accurate, or properly punctuated, making them hard to read and understand for people with hearing impairments. This fails WCAG 2.1 success criterion 1.2.2 (Captions (Pre-recorded)).
  • We plan to review captioning for all videos by August 2022. When we publish new content, we’ll make sure our videos have accurate captions.
  • Our pages and forms are generally well structured, there are a small number of pages where headings are not applied properly, inputs do not have text label elements, links are not grouped, iframe elements do not have titles, and a small number of pages do not have descriptive titles. This may make the structure of some pages harder to understand for people who use screen reader software. These fail WCAG 2.1 success criterion 1.3.1 (Info and Relationships) and 2.4.2 (Page Titled).
  • We plan to improve the structural components of the website by August 2022. When we publish new content, we’ll make sure structural elements meets accessibility standards.
  • On the first page of the donor application form, the pre-screener questions are radio buttons, and If No is accidentally selected, keyboard-only users are informed that they are not eligible without getting the chance to change their answer. This fails WCAG 2.1 success criterion 3.2.2 (On Input). Users can start over by refreshing the page.
  • We plan to improve keyboard operability by August 2022. When we publish new content we’ll make sure our use of images meets accessibility standards.
  • Some text elements are hidden until a button is clicked to reveal the content. For screen reader software users, that content is read out, whether shown on the screen or not. Conversely, some elements are identified as having hidden content when they do not. This fails WCAG 2.1 success criterion 1.3.2 (Meaningful Sequence) and 4.1.2 (Name, role, value).
  • We plan to improve the functionality of these components by August 2022.
  • On a small number of pages, the current location in the secondary navigation is only distinguished from the surrounding text by colour, which may make it hard for some people to distinguish from plain text. This fails WCAG 2.1 success criterion 1.4.1 (Use of colour).
  • We plan to make sure that no information is conveyed by colour alone by August 2022.
  • When a new page loads in the donor application form pages, keyboard focus may not be at the top of the page. This fails WCAG 2.1 success criterion2.4.3 (Focus Order).
  • We plan to make sure that when a new page loads, focus is always at the top of the page by August 2022.
  • A limited number of controls do not receive keyboard focus. On the Donor application form pages, progress bar elements receive keyboard focus when they should not. These fails WCAG 2.1 success criterion2.1.1 (Keyboard Navigation).
  • We plan to make sure that all appropriate controls are keyboard operable by August 2022.
  • On pages with forms, if an error is made, these errors are not automatically conveyed to screen reader software users in forms mode. By entering reading mode, however, error messages are discoverable. These fails WCAG 2.1 success criterion 1.3.1 (Info and Relationships).
  • We plan to make sure that all error messages are automatically conveyed to screen reader software users by August 2022.
  • On the donor application form – step 4, there is a link with the text, “here” that does not have sufficient context to be meaningful. This fails WCAG 2.1 success criterion 2.4.4 (Link purpose).
  • We plan to make sure that all links are meaningful by August 2022.
  • Contrast is generally excellent. There are, however, a small number of components that do not provide sufficient contrast. This fails WCAG 2.1 success criterion 1.4.3 (Colour contrast).
  • We plan to make sure that all components have sufficient colour contrast by August 2022.
  • In a form. the purpose of each input field that collects information about the user should be understood by assistive technologies. Some input elements are missing the necessary attributes for this to happen. This fails WCAG 2.1 success criterion 1.3.5 (Identify Input Purpose).
  • We plan to make sure that all relevant input elements have the appropriate values by August 2022.
  • When using the TAB key to navigate through the website, it must be possible to see keyboard focus on every element. This is not the case with a limited number of components. This fails WCAG 2.1 success criterion 2.4.7 (Focus Visible).
  • We plan to make sure that keyboard focus is visible on all buttons and links by August 2022.

PDFs and other documents

+
-

PDF documents have not yet been formally assessed for accessibility. If you need a document in a different format before they are reviewed, then please contact us to request one.

Preparation of this accessibility statement

This statement was prepared in September 2021.

This website was last tested in August 2021. The test was carried out by net-progress.

We used a sample approach to identify a range of representative pages to test.

Category

Governance