Accessibility statement for the Bridgit Digital Service
Published: 11 May 2026
Last updated: 24 June 2026
This accessibility statement applies to the Bridgit Digital Service, including the Bridgit web application and the related public pages used to access the service.
This service is run by Bridgit Care, part of Upstream Outcomes Ltd. We want as many carers, residents, professionals and partner organisations as possible to be able to use it.
The service includes features intended to support different access needs. Depending on the part of the service you are using, you should be able to:
- change colours, contrast and zoom using browser or device settings
- change text size using controls within the service
- navigate most of the service using a keyboard
- use most of the service with common screen readers and speech recognition software
- choose language preferences
- choose a preferred reading complexity
- choose reading support preferences, including Dyslexia Support
- choose reading speed preferences
- choose a shorter or simpler chat style where this is helpful
We also aim to keep content clear and easy to understand.
We have invested in voice and phone-based support so that people can access help without needing to use the digital application.
How accessible this service is
We have completed the majority of the development improvements identified through our April 2026 independent accessibility audit and subsequent technical review.
The June 2026 build includes improvements to:
- keyboard access and visible focus
- accessible names for buttons, ARIA buttons and interactive controls
- ARIA structure, including tablist and combobox behaviour
- screen reader support for status messages and dynamic content
- form labels, required-field messaging and instructions
- heading structure and programmatic page relationships
- decorative and informative image handling
- colour contrast and visual presentation
- spacing around interactive components
We know that some parts of the service are not yet fully accessible or still need independent validation. We are continuing to work on:
- minor colour contrast improvements in some areas
- making some advice-content links distinguishable by more than colour
- further checks on machine-readable heading and image text content
- clarifying and validating landmark structure in some parts of the service
- validating zoom and resize behaviour, including chat at 300% zoom
- reviewing remaining public website and WordPress-managed content issues
An independent accessibility reassessment is planned for July 2026. We will update this statement after that assessment.
If you experience a barrier using the service, contact us and we will do our best to provide support in another way.
Feedback and contact information
If you find any problems not listed on this page, or think we are not meeting accessibility requirements, contact us:
Email: contact@bridgit.care
Phone: +44 345 548 1654
When you contact us, it helps if you include:
- the page or feature you were using
- what device, browser or assistive technology you were using
- what went wrong
- what format or support would help you
We aim to acknowledge accessibility requests within 5 working days and tell you the next step.
Alternative formats and non-digital support
If you need information from Bridgit in a different format, contact us using the details above. We can discuss accessible digital formats and other support options, including accessible PDFs, plain text, large print, easy read, audio support and other reasonable adjustments where possible.
Bridgit is a digital service, but we recognise that not everyone can or wants to use an app or website. We have developed voice and phone support so people can access help without needing to use the digital application.
Where a carer needs wider non-digital support, or would benefit from support by phone or in person outside the digital tool, we recommend that they speak to their local carers service or the organisation that invited them to use Bridgit. We aim to work in partnership with local carers services so carers can access real-world support alongside digital support.
Reporting accessibility problems with this service
We are always looking to improve the accessibility of the Bridgit Digital Service. If you find a problem that is not listed on this page, please contact us using the email or phone number above.
Enforcement procedure
The Equality and Human Rights Commission is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
If this service is being provided to you through a public sector organisation and you are not happy with how your accessibility request or complaint has been handled, you can contact the Equality Advisory and Support Service.
Technical information about this service’s accessibility
Bridgit Care is committed to making the Bridgit Digital Service accessible and aims to meet the Web Content Accessibility Guidelines version 2.2 AA standard.
Where Bridgit is used by public sector partners, we aim to support those partners in meeting their accessibility obligations.
Compliance status
The Bridgit Digital Service has been tested against the Web Content Accessibility Guidelines version 2.2 AA standard.
This service is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, due to the non-compliances and items awaiting validation listed below.
We have completed the majority of the development improvements identified in the April 2026 independent accessibility audit. An independent reassessment is planned for July 2026 to validate the improvements and confirm any remaining non-compliances.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with accessibility standards
Some parts of the service do not fully meet WCAG 2.2 AA, or are awaiting independent validation following the June 2026 development release.
We are continuing to address these issues through our accessibility improvement programme and will update this statement after the July 2026 reassessment.
Page structure, labels and relationships
We have made improvements to headings, form labels, visual labels, required-field messaging, combobox associations and page relationships.
Some remaining public website or WordPress-managed content may still need improvements to list structure, input purpose, error-message relationships, visual labels or page relationships.
This may affect WCAG 2.2 success criteria including:
- 1.3.1 Info and Relationships
- 1.3.5 Identify Input Purpose
- 3.3.1 Error Identification
- 3.3.2 Labels or Instructions
- 3.3.3 Error Suggestion
We are reviewing the remaining items and will validate the changes through the July 2026 independent reassessment.
Keyboard access, focus order and focus visibility
We have delivered improvements to keyboard access and visible focus, including fixes to previously identified major keyboard-accessibility issues.
Some areas still need final validation, including focus order and focus visibility in a small number of public website or app areas.
This may affect WCAG 2.2 success criteria including:
- 2.1.1 Keyboard
- 2.4.3 Focus Order
- 2.4.7 Focus Visible
We will include these areas in the July 2026 independent reassessment.
Colour contrast and link identification
We have delivered colour contrast improvements across a number of text, resized-text and non-text interface elements.
A small number of minor visual issues remain in progress. These include a colour contrast adjustment where the current contrast is close to the required level, and advice-content hyperlinks that are being updated so they are distinguishable by more than colour.
This may affect WCAG 2.2 success criteria including:
- 1.4.1 Use of Colour
- 1.4.3 Contrast (Minimum)
- 1.4.11 Non-text Contrast
We are updating styles and link presentation to address these issues.
Images, headings and machine-readable text
We have improved the way decorative and informative images are handled, including decorative-image treatment and descriptive alternative text.
Some remaining machine-readable heading or image text content is being reviewed and refined.
This may affect WCAG 2.2 success criteria including:
- 1.1.1 Non-text Content
- 1.3.1 Info and Relationships
We will validate these improvements in the July 2026 independent reassessment.
Interactive components and screen reader announcements
We have delivered improvements to buttons, ARIA buttons, tablists, comboboxes, task controls, checkboxes, information buttons and dynamic status messages.
Some remaining public website or WordPress-managed interactive elements may still need final review to confirm their accessible name, role, value or status-message behaviour.
This may affect WCAG 2.2 success criteria including:
- 4.1.2 Name, Role, Value
- 4.1.3 Status Messages
We are continuing to improve component markup and screen reader announcements.
Zoom and resize behaviour
We have reviewed the chat experience at 300% zoom and currently consider it usable. No change is planned for that specific item at the moment.
We will ask the independent assessor to validate zoom and resize behaviour as part of the July 2026 reassessment.
This may affect WCAG 2.2 success criterion:
- 1.4.4 Resize Text
Disproportionate burden
We are not currently making any disproportionate burden claims for the core Bridgit Digital Service.
Content that is not within the scope of the accessibility regulations
Some content or services linked from Bridgit may be provided by third parties or local partner organisations. We do not always control these external websites, documents or services.
Where possible, we work with partners to encourage accessible content and support users who need information in another format.
What we are doing to improve accessibility
We are taking a number of actions to improve accessibility:
- completing the remaining minor improvements from the April 2026 independent accessibility audit
- validating the June 2026 development improvements through independent testing planned for July 2026
- updating colour contrast and hyperlink styling where minor issues remain
- reviewing remaining heading, landmark and machine-readable text issues
- reviewing remaining public website and WordPress-managed content issues
- continuing automated and manual accessibility testing
- improving our design and development processes so new features are checked for accessibility before release
- reviewing accessibility with carers, partners, local services and users
- continuing to develop voice and phone-based support so people can access help without needing to use the app
We will update this statement after the July 2026 independent reassessment and as further accessibility improvements are made.
Preparation of this accessibility statement
This statement was prepared on 11 May 2026. It was last reviewed and updated on 24 June 2026.
The Bridgit Digital Service was last independently tested in April 2026 against the WCAG 2.2 AA standard.
The April 2026 test was carried out by an independent accessibility tester. The test reviewed a sample of key areas of the service, including the landing page, onboarding and sign-in journeys, advice areas, side navigation, chat, toolkit, community and user profile areas.
Following that test, Bridgit delivered the majority of the identified development improvements through May and June 2026 releases.
A further independent accessibility assessment is planned for July 2026 to validate the completed improvements and identify any remaining issues.
We also use automated testing, manual review and user feedback to identify and fix accessibility issues.
We will review this statement again after the July 2026 independent reassessment and at least once a year.