Accessibility statement

Bridgewater Community Healthcare NHS Foundation Trust is committed to making its website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.

This accessibility statement applies to www.bridgewater.nhs.uk.

How you should be able to use this website

We want as many people as possible to be able to use this website. You should be able to:

  • change colours, contrast levels and fonts using browser or device settings
  • zoom in up to 400% without the text spilling off the screen
  • navigate most of the website using a keyboard or speech recognition software

Feedback and contact information

Tell us if you need information in a different format.

In your message, include:

  • the web address (URL) of the content
  • your email address and name
  • the format you need – for example, plain text, braille, BSL, large print or audio CD
  • You can also request a PDF in an accessible format

Reporting accessibility problems with this website

If you find any problems that are not listed on this page or you think we’re not meeting the accessibility requirements, you can contact us at bchft.patientservices@nhs.net.

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

Compliance status

This website is partially compliant with the Web Content Accessibility Guidelines (WCAG) version 2.2 AA standard.

Non-accessible content

Non-compliance with the accessibility regulations

The content listed below is non-accessible for the following reasons.

  1. Some tables are structured incorrectly, so screen readers cannot understand the relationships between information in the table. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
  2. Some headings do not display correctly. They may look like normal text or a different type of heading. This fails WCAG 2.2 success criterion 1.3.1 (Info and Relationships).
  3. Some images use colour as the only way to convey meaning. This fails WCAG 2.2 success criterion 1.4.1 (Use of Color).
  4. Some images include text with poor colour contrast to its background. This fails WCAG 2.2 success criterion 1.4.3 (Contrast (Minimum)).
  5. Some pages use images of text instead of text. This fails WCAG 2.2 success criterion 1.4.5 (Images of Text).
  6. Some images include elements with poor colour contrast to the background. This fails WCAG 2.2 success criterion 1.4.11 (Non-text Contrast).
  7. Some pages have duplicate titles. This may make it difficult for users to orient themselves and find the right content. This fails WCAG 2.2 success criterion 2.4.2 (Page Titled).
  8. Some headings don’t accurately describe the content underneath. This fails WCAG 2.2 success criterion 2.4.6 (Headings and Labels).
  9. The text on some buttons doesn’t accurately describe what the button does. This fails WCAG 2.2 success criterion 2.4.6 (Headings and Labels).
  10. Some images of text that are used as links have image descriptions that don’t include all of the text. This fails WCAG 2.2 success criterion 2.5.3 (Label in Name).
  11. Many documents are in PDF format. They are not accessible in a number of ways including missing document structure. This fails WCAG 1.3.1 Info and Relationships (PDF).
  12. The cookie banner link ‘Learn More’ does not have sufficient colour contrast when the keyboard tabs onto it. This fails WCAG 2.2 success criterion 1.4.3 (Contrast (Minimum)).

  13. When the cookie menu is minimised in the corner, the keyboard focus is not visible on this to expand it and the hidden information cannot be reached with a keyboard. This fails WCAG 2.2 success criterion 2.1.1 (Keyboard).

We are working to fix these issues by March 2026.

What we’re doing to improve accessibility

We are working alongside other government departments and agencies to fix content which fails to meet the Web Content Accessibility Guidelines version 2.2 AA standard.

Preparation of this accessibility statement

This statement was prepared on 18 November 2024. It was last reviewed on this date.

This website was last tested in November 2023 against the WCAG 2.2 AA standard. This test of a representative sample of pages was carried out by Government Digital Services.

We also used findings from our own testing when preparing this accessibility statement. This testing included using the ReachDeck Toolbar accessibility checker.

Last updated 15 December 2025.