This website is run by RNLI and Funraisin. We want as many people as possible to be able to use this website.
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:
Whole site
- Most text does not respond to an increase in text size.
- Navigation is not always consistent.
- Many buttons, links, menus and form fields do not have a focus state.
- Some focus states do not have sufficient colour contrast.
- There is no skip to main content button.
- There are images of text.
- Not all visual information is conveyed to people using a screen reader, or visual information is unclear for people using a screen reader. Many buttons and form fields are unlabelled.
- Some images and icons do not have a text alternative, so people using a screen reader cannot access the information. Some decorative images are not marked as decorative.
- Cannot access all text with a keyboard and screen reader.
- Many items do not have a visible focus when using a screen reader or the visible focus is in the wrong location on the page, or hidden by other page elements.
- Hover states are only indicated by a change of colour.
- There is an invalid ‘home’ role.
- Many buttons, links, hero components, headings titles are not included in an ARIA landmark.
Donation Form
- Some text does not have sufficient colour contrast.
- Error messages are often generic or missing.
- Tooltips are not clear.
- Cannot exit dropdown fields with a keyboard.
- After closing an error message pop up, focus order is confusing when using a keyboard or a keyboard and screen reader.
- Cannot access donation amount buttons with a keyboard or keyboard and screen reader.
- Personal donation and company donation radio buttons are hard to get past with a keyboard and a screen reader.
- User has to tab through each form step icon even if one has been selected when using a keyboard and screen reader.
- A link is missing text.
- Form steps are only indicated by a change of colour.
- Active states are only indicated by a change of colour.
- An ARIA label is unsupported or prohibited.
- A hidden element has focusable content.
Fundraiser Dashboard
- Some labels and buttons could be clearer.
- Error messages are often generic or missing.
- There are often no error suggestions.
- Some text does not have sufficient colour contrast.
- Dashboard pages do not have unique page titles.
- Cannot access or exit dropdown fields with a keyboard.
- Cannot access the calendar picker or landline or mobile buttons with a keyboard.
- Focus order can be confusing, especially when using lightboxes as the focus may not move to the light box, or may move behind the light box.
- When using keyboard, after closing ‘import contacts’ light box, focus is sent to the top of the page and not the next focusable item.
- On the My Fitness page, when using a keyboard or a keyboard and screen reader, the order of the activity fields is inconsistent with the visual layout.
- Cannot access the ‘copy url’ button and QR code window, with a keyboard, or keyboard and screen reader.
- Cannot exit dropdown fields with a screen reader.
- Cannot access instruction text under personal URL and Fundraising Target with a keyboard and screen reader.
- No error messages when using a keyboard and screen reader.
- Several links are unclear or hard to tell apart with a screen reader.
- Cannot access or close any lightboxes (pop ups) with a keyboard and screen reader.
- The profile menu does not open when using a keyboard and screen reader.
- Dropdowns are hard to navigate with a keyboard and screen reader.
- The ‘Postcode’ and ‘Number’ fields in the address finder don’t have labels.
- The RNLI logo in the footer sends viewport focus to the top of the page when using a screen reader.
- Active states are only indicated by a change of colour.
- Some headings are not structured or nested correctly.
- Selecting mobile icon button creates a change of context on input by adding a country code field.
- There is an invalid autocomplete token.
- Multiple elements are not contained inside the required context.
- There are instances of empty container elements.
- There are sections of text that are not included in an ARIA landmark.
Registration Form
- There is no warning before you delete a team member.
- Error messages are often generic or missing.
- Some headings and titles could be clearer.
- Some text does not have sufficient colour contrast.
- On the lifeboat station registration form, the ‘next step’ button on step 3 is actually a ‘finish’ button.
- Cannot access or exit dropdown fields with a keyboard.
- Cannot access ‘Already have an account’, ‘profile image’ or donation amounts with a keyboard.
- Focus order can be confusing, especially when using lightboxes as the focus may not move to the light box, or may move behind the light box or when using address finders when using a keyboard, or a keyboard and screen reader.
- Cannot delete group members whilst using a keyboard or using a keyboard and screen reader.
- Cannot exit dropdown fields with a screen reader.
- Cannot access profile image button with a keyboard and screen reader.
- When using a screen reader and submitting a form with errors, focus does not move to the first error.
- Some pages are missing a heading.
- Some headings are not structured or nested correctly.
- There is an instance of a visible label and programmatic name not matching on log in button.
- Some buttons don’t have a hover state.
- There is an empty heading.
- There is an invalid HTML element.
- There is an empty list box.
- There are multiple elements not inside the required context.
- There is a hidden element with focusable content.
- There is some unsupported ARIA.
Leaderboards
- Placeholder text is used as a label on search field which disappears when the user starts to type.
- Error messages are often generic or missing.
- Leaderboard cannot be paused.
Navigation and Footer
- Search field is labelled by prefill text which disappears when the user starts typing.
- When using a keyboard, mobile screen reader or keyboard and a screen reader, focus order can be confusing, or repetitive when using menus and navigation.
- Privacy policy and sitemap links are only identified by a change of colour.
- The RNLI logo in the footer sends viewport focus to the top of the page.
- Cannot access the Fundraising Regulator logo in the footer with a mobile screen reader.
- There is a header at the wrong level.
- There is an empty container element.
Other pages
- On the ‘Search for a Fundraiser’ page a form field is unlabelled and the prefill text disappears when a user starts to type.
- Several links are unclear or hard to tell apart.
- Some text does not have sufficient colour contrast.
- There is no error message on the forgotten password lightbox/pop-up if an invalid email format is used.
- Some animations cannot be paused, or only pause on hover.
- On the member log in, colour is used as the only way of conveying some information.
- Cannot access FAQs with a keyboard, or keyboard and screen reader.
- FAQ skip links do not work with a keyboard, or a screen reader and keyboard.
- When using a keyboard cannot switch between individual/teams and fundraisers/fitness views of leaderboards.
- Focus order can be confusing, especially when using lightboxes as the focus may not move to the light box, or may move behind the light box.
- Cannot access or close log in lightbox (pop up) with a keyboard and screen reader.
- Hard to get past donation tickers when using a mobile screen reader.
- Some field labels are confusing when using a keyboard and screenreader.
- ‘Amount raised’, ‘entrants’ and ‘distance’ on leaderboards are skipped over when using a mobile screen reader.
- On some pages visible focus is hidden for the rest of the page when using a mobile screen reader, as it is obscured by sticky donate and share buttons.
- When using a mobile screen reader, the user can’t see anything below the hero as sticky sign up button is in the way until viewport moves after the ticker.
- ‘Donate’ and ‘share’ buttons are hidden when they are first announced by a mobile screen reader.
- Some close buttons have no hover state.
- Some headings are not structured or nested correctly.
- There are roles which are not in the required context.
- There is a presentational iframe that is exposed to assistive technology.
- Share components have a hidden element with focusable content.
What to do if you cannot access parts of this website
If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:
- email supportercare@rnli.org.uk
- call 0300 300 9990 (UK)
- call 01 895 1800 (Ireland)
- fill in an enquiry form
We’ll consider your request and get back to you as soon as possible.
If you cannot view the map on our ‘contact us’ page, call or email us for directions.
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: digital@rnli.org.uk
Contacting us by phone or visiting us in person
Find out how to contact us.
Technical information about this website’s accessibility
The RNLI is committed to making its website accessible, in accordance with the Equality Act 2010.
This website is not compliant with the Web Content Accessibility Guidelines version 2.0 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 icons do not have a text alternative, so people using a screen reader cannot access the information. Some decorative images are not marked as decorative. This fails WCAG 2.0 success criterion 1.1.1 (non-text content).
Not all visual information is conveyed to people using a screen reader, or visual information is unclear for people using a screen reader. This fails WCAG 2.0 success criterion 1.3.1 (info and relationships).
Hover and active states are only indicated by a change of colour. Some links and form steps are only indicated by a change of colour. This fails WCAG 2.0 success criterion 1.4.1 (use of colour).
Some text and some focus states do not have sufficient colour contrast. This fails WCAG 2.0 success criterion 1.4.3 (contrast (minimum)).
Most text does not respond to an increase in text size. This fails WCAG 2.0 success criterion 1.4.4 (resize text).
There are some images of text. This fails WCAG 2.0 success criterion 1.4.5 (images of text).
Not all links, buttons, FAQs, form fields, lightboxes, menus or text can be accessed with a keyboard. This fails WCAG 2.0 success criterion 2.1.1 (keyboard).
Cannot close, or navigate away from, many dropdown fields or lightboxes, when using a keyboard. The donation ticket and some radio buttons are hard to navigate with a screen reader. This fails WCAG 2.0 success criterion 2.1.2 (no keyboard trap).
Some animations cannot be paused, or only pause on hover. This fails WCAG 2.0 success criterion 2.2.2 (pause, stop, hide).
There is no skip to main content button. FAQ skip links do not work. This fails WCAG 2.0 success criterion 2.4.1 (bypass blocks).
Some pages do not have an unique page title or are missing a page title. This fails WCAG 2.0 success criterion 2.4.2 (page titled).
Focus order can be confusing, especially when using lightboxes, menus, navigation and some forms and error messages. This fails WCAG 2.0 success criterion 2.4.3 (focus order) and success criterion 1.3.2 (meaningful sequence).
Several links are unclear or hard to tell apart. This fails WCAG 2.0 success criterion 2.4.4 (link purpose (in context)).
Some headings and labels could be made clearer. This fails WCAG 2.0 success criterion 2.4.6 (headings and labels).
Many buttons, links, menus and form fields do not have a focus state. Many items do not have a visible focus when using a screen reader or the visible focus is in the wrong location on the page, or hidden by other page elements. This fails WCAG 2.0 success criterion 2.4.7 (focus visible).
Navigation is not always consistent. This fails WCAG 2.0 success criterion 3.2.3 (consistent navigation).
Error messages are often generic or missing. This fails WCAG 2.0 success criterion 3.3.1 (error identification).
There are often no error suggestions. This fails WCAG 2.0 success criterion 3.3.3 (error suggestion).
There is no warning before you delete a team member. This fails WCAG 2.0 success criterion 3.3.4 (error prevention (legal, financial, data)).
Many headings are not structured or nested correctly. Many buttons have no hover state. There are instances of empty container elements. Multiple elements are not contained inside the required context. There are multiple empty list boxes. There is an instance of an invalid autocomplete token. There is an instance of invalid HTML. There is an instance of an empty heading. There is a presentational iframe exposed to assistive technology. There is an instance of a visible label and programmatic name not matching. This fails WCAG 2.0 success criterion 4.1.1 (parsing).
Many buttons, links, hero components, headings titles or text are not included in an ARIA landmark. There are instances of an invalid role. There are instances of unsupported or prohibited ARIA labels. There are some hidden elements with focusable content. There is a link missing a text alternative. This fails WCAG success criterion 4.1.2 (name, role, value).
How we tested this website
This website was last tested in 2025. The test was carried out by the RNLI.
We tested a sample of pages to cover as much functionality as possible, including sign up and donation journeys and fundraiser dashboards.
We tested:
- our Funraisin website platform, available at https://fundraise.rnli.org/
What we’re doing to improve accessibility
This statement was prepared on 22 July 2025. It was last updated on 22 July 2025.
