Designed to be used by everyone

Organisation: Deviant Botanicals Limited (trading as DevBot) · Products: dev-bot.co.uk, ambivalence.app · WCAG target: 2.2 Level AA · Last reviewed: 3 November 2026

This accessibility statement applies to the DevBot website (dev-bot.co.uk) and the ambivalence civic learning platform (ambivalence.app). It follows the model statement for the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, so that the public bodies who use ambivalence can rely on it. We want as many people as possible to be able to use our products.

How accessible ambivalence is

In ambivalence you can:

• open an accessibility panel from the floating accessibility button, or with Alt + A on any screen
• switch off the single-key shortcuts (H, L, E, P) if you use speech recognition or press keys by accident
• choose one of four text sizes, switch on high contrast, and reduce motion (the app also follows your device's reduced-motion and contrast settings)
• switch on subtitles for every episode; they are off until you turn them on, and your choice is remembered
• see a running word count while you write a reflection (screen readers are told once you have written enough to submit), and have obvious typing slips in English corrected as you go, with Backspace to undo each one; this can be switched off in the accessibility panel
• use the whole app with a keyboard, with a skip link and visible focus outlines
• use a screen reader: controls carry labels and roles, and changes are announced through a live region
• use the interface in five languages: English, French, German, Arabic (right to left) and Japanese

Your accessibility choices are kept in your browser, so they persist between visits on the same device.

Compliance status

ambivalence.app is partially compliant with WCAG 2.2 Level AA, because of the items listed below that are still under review. On dev-bot.co.uk our latest testing found no failures.

Non-accessible content

Non-compliance with the accessibility regulations

ambivalence.app

• Audio description. Episode video does not have audio description. The narration tells the story and the questions are on screen as text, so we believe little or nothing important is shown only in the picture, but we have not yet checked every scene to confirm it. Until we have, this may fail WCAG 1.2.5 (Audio Description, Prerecorded). We are keeping this under review as each episode is made, and where a picture carries meaning the narration does not, we will describe it in narration or text.
• Music and sound effects in subtitles. Subtitles cover all narration and dialogue but do not describe music or sound effects. We treat these as atmosphere rather than information. Where a sound does carry meaning in the story, leaving it out of the subtitles may fail WCAG 1.2.2 (Captions, Prerecorded), and we will add a description for it. We consider this when reviewing each episode.

dev-bot.co.uk

We are not aware of any content on dev-bot.co.uk that fails WCAG 2.2 AA.

Fixed since our last review

In October and November 2026 we fixed eight issues our reviews found:

• the single-key shortcuts (H, L, E and P) can now be switched off in the accessibility panel (WCAG 2.1.4)
• episode cards on the Learn screen no longer nest their Play and More info controls inside another control (WCAG 4.1.2)
• news cards in Look can now be reached and opened with a keyboard (WCAG 2.1.1)
• small grey labels on dev-bot.co.uk now meet the 4.5:1 contrast ratio (WCAG 1.4.3)
• links within body text on dev-bot.co.uk are now underlined (WCAG 1.4.1)
• buttons in the episode player (close, play, subtitles, subtitle language and settings) and the theme choices in the account panel now have accessible names (WCAG 4.1.2)
• the badge icons in the episode player are announced with the badge's name and whether you have earned it (WCAG 4.1.2)
• the scrollable list of learning themes beside the episode player can be reached and scrolled with a keyboard (WCAG 2.1.1)

Disproportionate burden

We are not claiming disproportionate burden for any content.

Content that is not within the scope of the accessibility regulations

The Deep Read view in Look shows articles from third-party news sources. We tidy their formatting into headings, paragraphs and lists, but we do not write or control that content, and some articles may have accessibility problems that come from the original source.

How we tested

On 26 October 2026 we:

• ran an automated check (axe-core 4.10, WCAG 2.0, 2.1 and 2.2 Level A and AA rules) on the dev-bot.co.uk home, licensing, trust and accessibility pages, and on the ambivalence home, Learn and Look screens
• reviewed the app's keyboard handling, accessibility panel, subtitle controls and timed elements against WCAG 2.2
• after fixing the issues found, re-ran the same automated check (no failures) and checked by keyboard that episode and news cards can be reached and opened, and that turning off single-key shortcuts takes effect

On 3 November 2026 we ran the same automated check on the signed-in screens: the learner's home screen, the account panel (progress, badges and badge sharing), the public badge verification page, the Learn screen, and the episode player, including a written reflection while empty, while being written, and after it is submitted. We fixed the three issues it found the same day, and a re-run found no failures.

During a Pilot, organisation administration (invitations, cohorts and reports) is carried out for the customer by DevBot, and reports are supplied as CSV files that open in any spreadsheet program. There is no customer-facing administration console yet. When one is released it will be tested before release and added to this statement.

What we're doing to improve accessibility

We review audio description and sound descriptions as each episode is made. We re-review this statement whenever a significant feature is released, and at least every six months.

Feedback and contact information

If you find any barrier in our products, or need information in a different format, email hello@dev-bot.co.uk with "Accessibility Feedback" in the subject. We aim to respond within 5 working days.

Enforcement procedure

The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. If you are not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).

Preparation of this statement

This statement was first prepared in March 2026. It was last reviewed on 3 November 2026.