adept

Accessibility statement

Last reviewed: 12 October 2026

Adept Training Platforms Ltd is committed to making its web application accessible, in line with the Web Content Accessibility Guidelines (WCAG) 2.2 level AA. This statement applies to the web application at manage.adept-platforms.com.

How accessible this application is

This application is partially conformant with WCAG 2.2 level AA: it meets most criteria, with the known exceptions listed below.

What currently works well:

  • Colour contrast of text meets the AA contrast ratio (4.5:1) in both the light and the dark theme, including the colours used for statuses. Form fields, selectors and filter chips have an outline that meets 3:1.
  • Text resizing - the app reflows and remains usable when you zoom the browser to 200%, and browser zoom is never blocked.
  • Keyboard operation - every form is operable with a keyboard, Tab moves through fields, selectors and actions in their logical order, and every button and icon control shows a clear focus ring.
  • Names for controls - every icon-only control (navigation arrows, pagers, filter chips, tick-boxes, timeline toggles, selectors, date pickers) exposes a descriptive name to screen readers. Filter chips announce whether they are selected.
  • Interactive target size - buttons, chips and icon controls on the screens a trainee uses on a phone give at least a 44 by 44 pixel target, as do icon buttons and the rotation pager everywhere. Some compact buttons on staff desktop screens are 32 pixels high, above the AA minimum of 24 by 24 pixels.
  • Timelines - the cohort and placement timelines scroll with the arrow keys and are described to screen readers.
  • Landmarks - every page has a navigation landmark (the sidebar) and a main landmark (the page content), so a screen reader can jump between them.
  • Visible structure - headings, cards and form fields have clear visual labels, and error / confirmation messages are shown in text (not by colour alone).
  • Personal data controls - you can download a copy of your data or request its deletion from your profile.

Known issues (we are working on these)

  • Screen-reader evaluation - control names and descriptions pass automated checks but have not yet been evaluated by ear with NVDA and VoiceOver. This is under way in October 2026.
  • Text spacing - text is drawn on a canvas, so a personal stylesheet that changes line, letter or word spacing has no effect. Browser zoom to 400% works and is the supported way to enlarge text.
  • Complex grids - the rotation and cohort grids, placement timelines and progress matrices carry a spoken description for each bar and cell, but do not yet convey every role, state and value to screen readers. This is the next phase of our roadmap.
  • PDF downloads are not tagged - the reports summary, the annual programme report and ARCP panel thank-you letters are untagged PDFs, so a screen reader may read them out of order. The report figures are also on screen in the application and download as a spreadsheet (.xlsx), and a thank-you letter can be asked for in another format using the contact details below.
  • Teaching check-in - check-in by QR code always offers a typed six-character code instead, so no camera is needed.
  • The application has not yet been independently audited to full WCAG 2.2 AA.

What we're doing to improve accessibility

  • Between 3 and 11 September 2026 we ran nine automated audits (axe-core) across every page of the application, on both the staging copy and the live service, and fixed every control they identified: keyboard focus order, focus visibility, target sizes, page zoom, timeline keyboard access and the names of icon-only controls.
  • On 4 October 2026 we re-audited every page each role can reach (programme director, college tutor, trainee, administrator, and the sign-in page) and fixed what was found: unnamed selectors and tick boxes, the show-password button on the sign-in page, and form fields that lost their name once filled in. We also calculated the contrast of every text colour in both themes, darkened the status colours that fell short as text, and added navigation and main landmarks, which the framework has only recently made possible.
  • On 5 October 2026 we tested with the keyboard alone, with every dialog and panel open, and at 400% zoom. Navigation, lists and panels worked by keyboard as found. We fixed: the outline of form fields, selectors and chips; the cohort timeline, which is now reached before its name column and shows a focus ring; the show-password button, now in the Tab order; and the names of dialogs, date pickers and the controls inside the allocation panel. No page cuts off text at 400% zoom.
  • On 10 October 2026 a full audit of the application's code led to these fixes: the timeline colours for training stages now meet 4.5:1 with their white labels; buttons that confirm a deletion or a warning keep a readable label in the dark theme; cards that stayed white in the dark theme now follow it; the smallest timeline labels are now 11 pixels, and on a phone the trainee's timeline also says in ordinary text where they are now and where they go next; four unnamed icon buttons were named; and error messages say what happened in plain words. Filter chips announce whether they are selected from the same date.
  • A formal three-phase WCAG 2.2 AA roadmap is in place: manual screen-reader and keyboard evaluation (NVDA and VoiceOver) in October 2026, semantic enrichment of the grids and timelines in November and December 2026, then an independent third-party audit in January 2027. Target completion: 31 January 2027.
  • Automated accessibility checks are repeated on every significant release.

Feedback and contact

If you find an accessibility barrier, or need information in a different format, contact support@adept-platforms.com. We aim to respond within 5 working days.

Enforcement

If you are not happy with how we respond, you can contact the Equality and Human Rights Commission (EHRC), which enforces the public-sector accessibility regulations.

Preparation of this statement

This statement was prepared on 30 June 2026 and last reviewed on 12 October 2026 following the September and October audits. It is based on a self-assessment of the application against WCAG 2.2 AA, supported by automated testing. It will be reviewed after the independent audit above, and at least annually.