Accessibility statement for Bleepy
Last reviewed 30 October 2026
This statement applies to the Bleepy website at bleepy.co.uk and to every organisation site that runs on Bleepy (web addresses ending in bleepy.co.uk), including sign-in, events, booking, attendance, feedback and certificates.
We want as many people as possible to be able to use Bleepy, whatever their disability or the device and assistive technology they use. This statement explains where Bleepy falls short and how to get help.
Using Bleepy
You should be able to:
- use Bleepy with a keyboard alone, with a "Skip to main content" link at the top of each page
- zoom in up to 400% or use a phone-width screen, with most pages fitting the screen without scrolling sideways
- choose light or dark mode once signed in (a few pages still show light content)
- pause the moving parts of the homepage and other animations; if your device is set to reduce motion, they stay still
- type the check-in code shown under a session's QR code instead of scanning it
- add your communication needs to your profile, so the staff running the sessions you book can see them
- watch the help videos with a spoken guide and English captions, or read the written guide next to each one instead
How accessible Bleepy is
We know some parts of Bleepy are not fully accessible:
- With very large text (200%) or on a narrow screen, a few tables and calendar grids, such as the rooms week view, still scroll sideways inside their own area. On the bleepy.co.uk homepage, some text can be cut off when letter and word spacing is increased.
- Some pages may still have text or controls with too little contrast, or buttons smaller than recommended. We fix these as we find them.
- PDF documents, such as invoices, receipts and reports, have real text, a title and a language, but they are not tagged, so a screen reader may read their tables and headings as plain text. Certificates are pictures; the same details are on the My certificates page, in the certificate email and on the certificate check page.
- Videos and sound files that an organisation adds have captions and a transcript only when the organisation provides them. Bleepy gives staff a place to add both. Videos linked from YouTube or Vimeo use those sites' own captions.
Feedback and contact information
If you need information from Bleepy in a different format, such as large print, or your certificate as text, email support@bleepy.co.uk. Tell us what you need and the page or certificate it is about. We will reply within 5 working days.
If you use Bleepy through your organisation, for example your teaching or education team, you can also contact them directly.
Reporting accessibility problems
We are always looking to improve. If you find a problem that is not listed here, or think we are not meeting accessibility requirements, email support@bleepy.co.uk or use the contact form. We aim to acknowledge your message within 2 working days (Monday to Friday, 09:00 to 17:00 UK time).
Enforcement procedure
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the accessibility regulations. If you are not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS). In Northern Ireland, contact the Equality Commission for Northern Ireland.
Bleepy is not itself a public sector body. If the organisation that runs your Bleepy site is one, the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 apply to it, and you can also raise your complaint with that organisation. Everyone using Bleepy is covered by the Equality Act 2010.
Technical information about accessibility
Compliance status
Bleepy is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, because of the non-compliances listed below.
Non-compliance with the accessibility regulations
| Problem | WCAG 2.2 criterion |
|---|---|
| With very large text (200%) or on a narrow screen, a few tables and calendar grids, such as the rooms week view, still scroll sideways inside their own area. On the bleepy.co.uk homepage, some text can be cut off when letter and word spacing is increased. | 1.4.10 Reflow1.4.12 Text Spacing |
| Some pages may still have text or controls with too little contrast, or buttons smaller than recommended. We fix these as we find them. | 1.4.3 Contrast (Minimum)2.5.8 Target Size (Minimum) |
| PDF documents, such as invoices, receipts and reports, have real text, a title and a language, but they are not tagged, so a screen reader may read their tables and headings as plain text. Certificates are pictures; the same details are on the My certificates page, in the certificate email and on the certificate check page. | 1.3.1 Info and Relationships |
| Videos and sound files that an organisation adds have captions and a transcript only when the organisation provides them. Bleepy gives staff a place to add both. Videos linked from YouTube or Vimeo use those sites' own captions. | 1.2.1 Audio-only and Video-only1.2.2 Captions (Prerecorded) |
Disproportionate burden
We are not claiming disproportionate burden for any of the problems above.
Content that's not within the scope of the regulations
Videos that an organisation links from YouTube or Vimeo are shown in those sites' own players, with their own captions and controls. Bleepy does not control how accessible those players are.
What we are doing to improve accessibility
We plan to fix the problems listed above by 31 March 2027. We fix them as part of our regular releases, starting with the pages learners use most. In October 2026 we checked 119 pages in light and dark mode, at desktop and phone sizes, with automated tools and keyboard-only testing, and fixed most of what we found. A second full check on 25 October 2026 looked at every page for each kind of account, at 200% text and with wider text spacing, and checked forms, booking, check-in, pop-ups and documents by hand. Everything it found has been fixed apart from the problems listed above. Automated accessibility checks exist for our main public pages. We are extending them so they run before every release.
Preparation of this statement
This statement was prepared on 21 September 2026. It was last reviewed on 30 October 2026. The service was last tested on 25 October 2026, by the Bleepy team, against WCAG 2.2 AA; this was not an independent audit. Screen readers have not yet been part of the test. We will review it again by 25 April 2027, or sooner after major changes.