Accessibility statement for Epona Cares (PBS Centre of Excellence)
This statement applies to the Epona Positive Behaviour Support platform at app.epona.care. Epona is committed to making the platform accessible, in line with the Web Content Accessibility Guidelines (WCAG) version 2.2, Level AA.
Conformance status
This platform is partially conformant with WCAG 2.2 Level AA. Partially conformant means that some parts of it do not yet fully conform. They are listed under known limitations.
How accessible this platform is
What is in place today. The WCAG success criteria each item answers are shown in brackets.
Finding your way around
- A “Skip to main content” link is the first thing you reach with the keyboard on every page (2.4.1 Bypass Blocks).
- Every page has its own title, which screen readers announce when the page changes (2.4.2 Page Titled).
- The language of every page is declared, so screen readers read it in the right voice (3.1.1 Language of Page).
- A visible outline shows which item has keyboard focus (2.4.7 Focus Visible).
- Cards and list rows that open a record can be reached and opened with the keyboard, not only with a mouse (2.1.1 Keyboard).
- Dialogs keep keyboard focus inside them while they are open, close with the Escape key, and return focus to where you were when they close. Every dialog that can be dismissed has a visible Close button (2.1.2 No Keyboard Trap, 2.4.3 Focus Order, 2.4.11 Focus Not Obscured (Minimum)).
- Checkboxes, radio buttons and buttons are at least 24 by 24 pixels. This is set once for the whole platform, and measured in real browsers whenever the platform changes (2.5.8 Target Size (Minimum)).
Forms and signing in
- Form fields have labels that screen readers announce. An automated check, run whenever the platform changes, finds no form field without an accessible name (1.3.1 Info and Relationships, 3.3.2 Labels or Instructions, 4.1.2 Name, Role, Value).
- Fields for your own details — signing in, your profile and changing your password — tell your browser what they are for, so it can fill them in for you (1.3.5 Identify Input Purpose).
- Signing in has no puzzle to solve. Password managers can fill in your email address and password, and the code from your authenticator app can be pasted or filled in automatically (3.3.8 Accessible Authentication (Minimum)).
- When a field built with the platform’s standard form components has an error, the field is marked as invalid, the message is linked to it, and screen readers announce it (3.3.1 Error Identification).
- Confirmations and error messages that pop up are announced by screen readers without moving your focus, and so are the assistant’s replies (4.1.3 Status Messages).
Seeing and hearing content
- After an audit of the light theme, muted text and the borders of form fields were darkened to meet the contrast minimums (1.4.3 Contrast (Minimum), 1.4.11 Non-text Contrast).
- Voice notes are transcribed automatically on Epona’s own server. The transcript is shown with the recording in the document viewer, where a member of staff checks it against the recording. A transcript typed by the person making the recording is shown there too (1.2.1 Audio-only and Video-only (Prerecorded)).
- Animations and transitions are switched off if you have asked your device to reduce motion. This is good practice rather than a Level AA requirement.
- You can choose a light or dark theme, or follow your device’s setting, in Settings, then Preferences.
Documents
- The PBS plan, the monthly report and the analytics dashboard download as tagged PDFs. Their headings can be navigated, their tables keep their column headings, their reading order is declared, and each has a title and declares its language. They are made to the PDF/UA accessibility standard (1.3.1 Info and Relationships, 1.3.2 Meaningful Sequence, 2.4.2 Page Titled).
Known limitations
These parts of the platform are not yet fully accessible.
Photos and video
WCAG criteria affected: 1.1.1 Non-text Content, 1.2.2 Captions (Prerecorded), 1.2.3 Audio Description or Media Alternative (Prerecorded), 1.2.5 Audio Description (Prerecorded)
Images in the document viewer are described to screen readers only by the document’s title or file name, not by what they show. Photos added with “Add photos or video” are given an automatic title: “Photo” and the date and time. The optional description entered with an upload covers every file in it and is not used as a photo’s text alternative.
Videos cannot be played within the platform; they are downloaded to be watched. They have no captions, transcript or audio description.
Voice note transcripts
WCAG criteria affected: 1.2.1 Audio-only and Video-only (Prerecorded)
A voice note’s automatic transcript is machine text and can mishear words. It is marked as not yet checked until a member of staff has listened to the recording and confirmed or corrected it. A recording has no transcript if no speech is detected in it, or until the transcription service has processed it.
PDF documents that are not tagged
WCAG criteria affected: 1.1.1 Non-text Content, 1.3.1 Info and Relationships
The care plan, the PBS summary, the PBS grab sheet and the PERMA profile PDFs, and the PDFs the document scanner creates, are not tagged. Each has a title and declares its language, and its text is read in the order it appears on the page. But a screen reader cannot move between its headings, its tables lose the link between each cell and its column heading, and any images in it have no text alternative.
The scanner saves two copies of what it scans: one with the text read from the pages, and one of the page images alone, which has no text at all.
Documents that people upload, such as letters and reports from other organisations, are kept as they were received, and may not be accessible.
Testing with assistive technology
WCAG criteria affected: potentially any; in particular 1.3.1 Info and Relationships, 4.1.2 Name, Role, Value and 4.1.3 Status Messages
The platform has not yet had a full manual test with assistive technology. Some screens, such as the PBS plan editor, have been checked with VoiceOver on a Mac and the problems found were fixed. A full pass with screen readers, speech recognition and screen magnification is still to be done, and may find problems that automated checks and code review cannot.
Zoom, reflow and text spacing on data-dense pages
WCAG criteria affected: 1.4.4 Resize Text, 1.4.10 Reflow, 1.4.12 Text Spacing
An automated check makes sure nothing in the platform has a fixed width over 320 pixels, and that wide tables scroll within their own area rather than being cut off. But the pages dense with data — tables, the plan editor and the analytics dashboard — have not yet been assessed at 200% and 400% zoom or with increased text spacing. On them, some content may overlap, be cut off, or need scrolling in two directions.
Colour contrast in the dark theme
WCAG criteria affected: 1.4.3 Contrast (Minimum), 1.4.11 Non-text Contrast
Colour contrast was audited in the light theme. Problems in the dark theme have been found and fixed since, such as form fields and text that stayed black on a dark background, but the dark theme has not yet had an audit of its own. If you find something hard to read, the light theme is the one that has been checked.
Error messages in older forms
WCAG criteria affected: 3.3.1 Error Identification, 4.1.3 Status Messages
Some older forms still use fields that are not built on the platform’s standard form components. Their error messages may not be linked to the field or announced by screen readers. These fields are being moved onto the standard components.
How we tested this platform
- Automated checks run on every proposed change to the platform:
- axe-core accessibility checks of the shared form and card components. These check components, not whole pages, and cannot check colour contrast.
- Checks of the source code: that every form field has an accessible name, every dialog is built on the accessible dialog component, status messages stay announced, wide tables are not cut off, and form fields keep a readable text colour in the dark theme.
- Target sizes measured in real browsers (Chromium, Firefox and WebKit) on the sign-in page and on this statement, together with the style rule that sets them for the whole platform.
- The markup the tagged PDFs are printed from: one title, headings that do not skip a level, and table headings that declare what they head.
- A colour-contrast check of rendered pages on our test system, in the light theme, in August 2026: after muted text was darkened, 124 text elements on three pages were measured and none fell below the minimum.
- A review of the code against WCAG 2.2 Level AA, in August 2026, covering what can be checked in the code: page language, headings and landmarks, text alternatives for images, labels for form fields, and the roles and states of custom controls. What it found has been fixed or is listed above as a known limitation. Criteria that can only be checked by using the platform, such as keyboard and screen-reader use, are covered by the manual checks below and the test still to be done.
- The tagged PDFs were checked with veraPDF against PDF/UA-1 (ISO 14289-1) in September 2026, using plans, reports and analytics downloads from our test system.
- Manual checks of some screens with VoiceOver on a Mac. A full manual test with assistive technology has not yet been done.
Preparation of this statement
This statement was prepared on . It was last reviewed on . It applies to app.epona.care.
We review this statement after the manual test with assistive technology described above, and at least every six months, so the next review is due by . Each review checks every claim here against the platform as it is at the time.
Feedback and contact information
If you find a problem that is not listed here, or you cannot use part of the platform, please tell us. We will respond within 5 working days.
To tell us, sign in and raise a support ticket (choose Support in the menu, then New Ticket). Say which page you were on, what you were trying to do, and which device, browser and any assistive technology you were using.
If you cannot raise a ticket yourself — for example because you cannot sign in, or because you have a Family Member or Viewer account, which cannot raise tickets — please ask an administrator at your organisation to raise one for you.