Policy Center
Last Updated:
13 October 2026
Issue Number:
1.0
Classification
Company
Accessibility Statement for Audiebant Control
This statement applies to the Audiebant Control web application. That covers the sign-in and password reset pages and the operator interface used to manage announcements, schedules, zones, contacts, lone-worker safety, Audiesafe, AudieScreen digital signage and mass communications. It also covers the acknowledgement page that message recipients open from a link.
It does not cover the Audiebant mobile apps, player devices or signage screens. These have not been assessed yet; they will be, and will get their own accessibility statement. It also does not cover content that your organisation uploads, such as audio, message text and images.
Audiebant Control is run by Audiebant. We want as many people as possible to be able to use it. For example, you should be able to:
- zoom in up to 200% without text spilling off the screen
- navigate most of the application using just a keyboard, with a visible focus indicator
- use a skip link to jump past the navigation to the main content
- use a password manager and paste into sign-in fields
- sign in with a passkey instead of remembering a password
- use a light or dark theme
How accessible Audiebant Control is
We know some parts of Audiebant Control are not fully accessible:
- some text has too little contrast against its background. This mostly affects status badges, coloured labels, calendar entries and headings in the dark theme
- on a narrow screen, or when zoomed to 400%, some pages need sideways scrolling. This affects the tab bars on Settings, System Settings and Incidents, and the toolbar on the Audio Centre
- some form fields are not announced properly by screen readers. This affects the row selection boxes on the schedule lists, the start time fields on new schedules and the repeat slider on general announcements
- the recipient acknowledgement page does not declare its language, so screen readers may read it with the wrong pronunciation
- some controls inside pop-up dialogues and step-by-step wizards may not have names that screen readers can announce
- urgent incident alerts may not be announced straight away to screen-reader users
- we have not yet fully tested the application with screen readers, at 400% zoom or with custom text spacing
Feedback and contact information
If you need information from Audiebant Control in a different format, such as accessible PDF, large print or plain text, contact us:
- email: accessibility@audiebant.co.uk
- phone: 03331 882 324
- post: Audiebant Ltd, Unit 2, The Crossroads Business Park, Freckleton Street, Kirkham, PR4 2SH
We will reply within 3 working days.
Reporting accessibility problems
We are always looking to improve accessibility. If you find a problem not listed on this page, or think we are not meeting accessibility requirements, email accessibility@audiebant.co.uk. Tell us the page, what you were trying to do and any assistive technology you use. We log every report as a defect and assess it against the relevant WCAG success criterion.
Enforcement procedure
In the UK, the Equality and Human Rights Commission (EHRC) enforces the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. If your organisation uses Audiebant Control as a public-sector body and 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.
Technical information about this application’s accessibility
Audiebant is committed to making Audiebant Control accessible, in line with WCAG 2.2 Level AA. WCAG 2.2 AA is the standard behind the UK Public Sector Bodies Accessibility Regulations 2018, EN 301 549 and Section 508.
Compliance status
Audiebant Control is partially compliant with the Web Content Accessibility Guidelines version 2.2 AA standard, because of the non-compliances listed below.
Non-accessible content
The content listed below is not accessible, for the reasons shown.
Non-compliance with the accessibility regulations
Barrier | Where | WCAG 2.2 criterion | We plan to fix by |
|---|---|---|---|
Row selection checkboxes have no accessible name, so screen readers announce only “checkbox” | Playlist, bell and single-audio schedule lists | 1.3.1, 3.3.2, 4.1.2 | 7 November 2026 |
Start time fields and the repeat slider have no accessible name | New bell and single-audio schedules; general announcements | 1.3.1, 3.3.2, 4.1.2 | 7 November 2026 |
The page does not declare its language | Recipient acknowledgement page | 3.1.1 | 7 November 2026 |
Urgent incident alerts are not announced straight away to screen-reader users | Lone-worker incidents | 4.1.3 | 30 November 2026 |
Text contrast is below 4.5:1, mainly status badges, colour-coded labels, calendar entries, inactive tabs and blue headings in the dark theme | Across the interface, worst on Dashboard, Calendar and Incidents | 1.4.3 | 31 December 2026 |
At 400% zoom or 320px width, tab bars and toolbars force sideways scrolling | Settings, System Settings, Incidents, Audio Centre, Schedule exemptions | 1.4.10 | 31 December 2026 |
Some visible field labels are not linked to their fields in code | Operator forms | 1.3.1, 2.4.6, 3.3.2 | 31 December 2026 |
Some controls inside pop-up dialogues and wizards have no accessible name | Dialogues and multi-step wizards | 4.1.2 | 31 December 2026 |
Disproportionate burden
We are not claiming disproportionate burden for any content.
Content that is not within the scope of the regulations
Audio, message text and images that your organisation uploads are its own content. Audiebant Control does not alter or obstruct that content, and its accessibility remains your organisation’s responsibility.
What we’re doing to improve accessibility
Accessibility fixes are tracked on the same backlog as other defects, with an owner and a target release. Colour, spacing, focus and control sizes come from one shared theme, so a fix made there applies across the whole application.
We are adding automated accessibility checks to every release, so a fix cannot be undone by later work without us knowing. By 31 December 2026 we will also complete a manual evaluation using the W3C WCAG-EM method. It will cover screen-reader use of the core workflows, 400% zoom, text spacing, focus order and the five criteria new in WCAG 2.2. We will update this statement with the results.
Preparation of this accessibility statement
This statement was prepared on 13 October 2026 and last reviewed on 13 October 2026.
Audiebant Control release 20 was last tested on 13 October 2026 by Audiebant engineering. We tested 42 pages in both the light and dark themes with the axe-core 4.13 rule engine against WCAG 2.0, 2.1 and 2.2 A and AA. We also measured each page at a 320px viewport for reflow, and checked that every keyboard focus stop on the dashboard has a visible indicator.
We will review this statement at least every 12 months, and after each manual evaluation.