Accessibility Statement for GP Widget

Scope

This accessibility statement applies to the GP Widget marketing website at https://gpwidget.com and the GP Widget web application at https://app.gpwidget.com.

Our commitment

We want as many people as possible to be able to use GP Widget. This includes people with visual, hearing, motor, and cognitive impairments. We aim to make our websites and web application accessible and usable, and we continuously improve accessibility as we iterate the product.

Compliance status

GP Widget is being developed to meet the Web Content Accessibility Guidelines (WCAG) 2.2 level AA. Accessibility is treated as a continuous part of our software development lifecycle rather than a one-off exercise: every release is checked against the WCAG 2.2 AA success criteria using automated tooling, and any issues identified are tracked and addressed as part of normal product work.

How we test and improve accessibility

Accessibility is built into both our design and engineering processes. Every key page and feature in the GP Widget application is regularly scanned against the full set of WCAG 2.0, 2.1 and 2.2 A and AA success criteria, plus a wider best-practice ruleset, using the industry-standard axe-core accessibility engine (Deque Systems) executed against headless Chromium via Puppeteer. The scans cover authenticated and unauthenticated user journeys — including login, dashboard, search, guides, collections, audits, social prescribing, insights, profile, account settings and organisation administration — and produce dated evidence reports that are stored alongside the codebase.

Findings are reviewed by P Ridley (UX Designer) and the engineering team and resolved iteratively as part of the standard release cycle. The same scan is re-run after fixes to confirm regressions have not been introduced, and the process runs again on every meaningful change to the user interface so that accessibility is continuously verified rather than measured at a single point in time.

This is complemented by manual reviews covering keyboard navigation, focus order, screen-reader spot-checks (NVDA on Windows and VoiceOver on macOS) and content reflow at 320 px width — areas which automated tooling cannot fully evaluate. Together, the automated scans and manual checks give us ongoing, evidence-backed assurance that GP Widget remains accessible to users, including those relying on assistive technologies.

Non-accessible content and known issues

We are actively reviewing and addressing accessibility issues. The following items are known areas for improvement:

  • Image text alternatives: some images, particularly partner or customer logos, may use generic alternative text which is not as descriptive as it could be for screen reader users.
  • JavaScript dependency in the web application: the GP Widget application is a modern web application and requires JavaScript to load and operate. If JavaScript is disabled, content may not be available.

If you identify any other issues, please report them using the contact details below. We will prioritise fixes based on user impact and risk.

What to do if you cannot access parts of GP Widget

If you need information in a different format, or you are unable to use part of the website or application, contact us and we will work with you to provide an accessible alternative.

Email: info@gpwidget.com

We aim to respond within 5 working days. Requests are handled through our support process.

Reporting accessibility problems

We are always looking to improve accessibility. If you find any problems not listed on this page, or you think we are not meeting accessibility requirements, please email info@gpwidget.com with:

  • the page URL
  • what you were trying to do
  • what assistive technology or browser you are using (if relevant)

Enforcement procedure

If you are not satisfied with how we respond to your accessibility request or complaint, you can contact the Equality Advisory and Support Service (EASS): https://www.equalityadvisoryservice.com/

Preparation of this statement

This statement was prepared on 29 January 2026.

It will be reviewed by 29 January 2027, or sooner if significant changes are made to the service.