Accessibility statement

This website is run by the Stroke Association. We want as many people as possible to be able to use this website. For example, that means you should be able to:

• 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’ve also made the website text as simple as possible to understand.

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

If you need information on this website in a different format like accessible PDF, large print, easy read, audio recording or braille:

• email helpline@stroke.org.uk

• call 0303 3033 100

If you contact us by email we’ll get back to you within five working 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, please email website@stroke.org.uk or call our supporter care team on 0300 3300 740. 

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

Contacting us by phone 

Find out how to contact us.

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

• Colour contrast

1. Not all important graphical objects, interface components, and states have a colour contrast of 3:1. This fails WCAG 2.1 success criterion 1.4.3 (contrast minimum). Our plan to correct instances of this issue is detailed in our roadmap.

2. Not all of the text has sufficient contrast against the background colour. This fails WCAG 2.1 success criterion 1.4.3 (contrast minimum). Our plan to correct instances of this issue is detailed in our roadmap.

3. Colour is sometimes used as the only way to convey some information. This fails WCAG 2.1 success criterion 1.4.1 (use of colour). Our plan to correct instances of this issue is detailed in our roadmap. 

• Text and descriptions

4. The purpose of every link is not clear from its link text. This fails WCAG 2.1 success criterion 2.4.2 (link purpose). We plan to make improvements to link text as part of our next scheduled content audit, due to take place January to March 2021. When we publish new content we’ll make sure our use of link text meets accessibility standards.

5. Not all headings and labels are clear and descriptive. This fails WCAG 2.1 success criterion 2.4.6 (headings and labels). We plan to make improvements to headings and labels as part of our next scheduled content audit, due to take place January to March 2021. When we publish new content we’ll make sure our use of headings and labels meets accessibility standards.

6. Not all images have an appropriate text equivalent. This fails WCAG 2.1 success criterion 1.1.1 (non-text content). We plan to ensure text alternatives are added where missing as part of our next scheduled content audit, due to take place January to March 2021. When we publish new content we’ll make sure our use of images meets accessibility standards.

• Operational

7. Some menus, links, buttons, and other controls cannot be operated by keyboard. This fails WCAG 2.1 success criterion 2.1.1 (keyboard). Our plan to correct instances of this issue is detailed in our roadmap.

8. When using a keyboard to move through a page can it is not always easy to tell where you are. This fails WCAG 2.1 success criterion 2.4.3 (focus order). Our plan to correct instances of this issue is detailed in our roadmap.

9. Not all forms provide helpful, understandable error and verification messages. This fails WCAG 2.1 success criterion 3.3.1 (error identification).  Our plan to correct instances of this issue is detailed in our roadmap.

This statement was prepared on 21 August 2020. It was last reviewed 23 September 2020.

This website was last tested in July 2020. The test was carried out by the Stroke Association’s Digital team.

To conduct the test we sampled one representative live example of each of the page and form templates used on this website.