This statement applies to our website: https://www.headwaybristol.org.uk. 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 using browser or device settings (the Userway widget at the bottom left of the screen can support you with this).
- zoom in up to 400% without the text spilling off the screen
- navigate most of the website using a keyboard or 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.
How accessible is this website?
We know PDFs may not be accessible, and not all images have useful alternative text. We plan to remedy this going forwards and will fix old instances as we can.
Feedback and contact information
If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact [email protected], or call us on 0117 462 6962.
If you need information on this website in a different format (like accessible PDF, large print, easy read, audio recording or braille) please contact [email protected], or call us on 0117 462 6962.
We’ll consider your request and get back to you as soon as we can, but in no more than 10 days.
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).
Technical information about this website’s accessibility
Headway Bristol is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Compliance status
We are currently testing this website against the Web Content Accessibility Guidelines (WCAG) 2.2 AA standard.
We have used the WAVE tool to test the site, and solved any errors highlighted. Google’s PageSpeed Insights gives us an accessibility score of 98/100.
Based on this, we currently believe our site to be partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances listed below.
Non-compliance with the accessibility regulations
Some images do not have a text alternative, so people using a screen reader cannot access the information. This fails WCAG 2.2 success criterion 1.1.1 (non-text content).
We plan to add text alternatives for all images in 2026. When we publish new content, we’ll make sure our use of images meets accessibility standards. If you have a question about an image, please contact [email protected], or call us on 0117 462 6962.
Many of our older PDF documents are not fully accessible to screen reader software. They may lack the internal structure (tags) required for screen readers to understand the reading order, headings, and relationships between content. This fails WCAG 2.2 success criteria: WCAG 1.3.1 (Info and Relationships), WCAG 1.1.1 (Non-text Content) and WCAG 1.3.2 (Meaningful Sequence). Some may also fail WCAG 1.3.1 (Info and Relationships).
We plan to publish documents as HTML going forwards, and will update important historical documents wherever we find them.
If you need information on this website in a different format (like accessible PDF, large print, easy read, audio recording or braille) please contact [email protected], or call us on 0117 462 6962.
We’ll consider your request and get back to you as soon as we can, but in no more than 10 days
What we’re doing to improve accessibility
We’re currently testing the site and aim to fix any remaining non-compliant content in 2026. We plan to survey our Service Users for their opinions on the website in 2026, and we welcome input from all users via the contact details given in this statement.
Preparation of this accessibility statement
This website was last tested against the WCAG 2.2 AA standard on 3 March 2026.
We carried out the test using automated testing tools.
This statement was prepared on 3 March. It will be reviewed annually.
A full report will be published in 2026.