Our commitment
ARCADEBOX.AI is run by Ailora Limited (company no. 16660447, 71-75 Shelton Street, Covent Garden, London WC2H 9JQ, United Kingdom). Our whole idea is that anyone can make a game — and "anyone" has to include people who use a keyboard instead of a mouse, people who need higher contrast, people who get motion-sick, and people who use assistive technology.
This page is an honest statement of where we are: what already works, what doesn't yet, and how to tell us when something gets in your way. It covers the ARCADEBOX.AI website and the browser-based Studio at arcadebox.ai.
1. The standard we work towards
We use the Web Content Accessibility Guidelines (WCAG) 2.1, level AA as our reference standard, and we design new features with the European Accessibility Act's requirements in view.
We do not claim full WCAG 2.1 AA conformance today. ARCADEBOX.AI is partially conformant: much of the site meets the guidelines, and the known gaps are listed in sections 3 and 4 below. We'd rather tell you that plainly than publish a conformance badge we haven't earned. We work through the gaps as part of ordinary product development, and this page is updated as they close.
2. What works today
- Keyboard access. Site navigation, sign-in and sign-up, menus, and the Studio's main controls (chat, menus, the Builder panel) can be operated with a keyboard. Interactive controls show a visible focus ring.
- Reduced motion. Where the interface uses decorative animation, we respect your operating system's "reduce motion" setting (
prefers-reduced-motion) and switch the animation off. - Contrast and themes. The site ships light and dark themes, and interface text is designed against WCAG AA contrast targets. Your theme choice is remembered.
- Text and structure. Pages use semantic HTML headings, labelled form fields, and alt text or ARIA labels on meaningful icons and controls. Text can be resized with your browser's zoom without breaking the layout.
- No time pressure on the site itself. Nothing on the website (outside games) requires timed responses, and nothing flashes at seizure-inducing rates.
- Plain English. We write interface copy and legal pages in plain English, without jargon walls.
3. Known limitations
These are the honest gaps we know about on our own interface:
- Screen-reader coverage is uneven. Core flows (signing in, browsing, account settings) are usable with a screen reader, but some richer Studio panels — the live game preview, the model library, drag-and-drop placement — are not yet fully announced or operable with one.
- Some controls are icon-first. A few compact toolbar controls rely on tooltips for their labels; we're adding proper accessible names as we touch each area.
- Colour is occasionally the main signal. A few status indicators (for example build-progress states) lean on colour more than they should; text equivalents are being added.
- Voice features are optional extras, not requirements. Anything BIT can say out loud is also shown as text — but the reverse isn't always true yet.
4. Games and user-generated content
Most of what you play on ARCADEBOX.AI is made by other users, and games render inside a canvas element — a drawing surface that screen readers can't see into. That has two honest consequences:
- Canvas games have limited screen-reader support. The game page around a game (title, description, comments, scoreboards) is regular HTML and accessible; the game itself generally is not. This is a limitation shared by essentially all browser game engines today.
- We don't control the accessibility of user-made games. A creator's game may use colour combinations, flashing effects, small text, or control schemes we wouldn't choose. We ask creators to keep their games playable for as many people as possible, but we can't guarantee any individual game meets WCAG.
Where we control the defaults — the engines and templates games are built from — we aim for keyboard-plus-mouse controls, pause menus, and adjustable volume, so games start from a reasonable baseline.
5. Tell us what's in your way
If any part of ARCADEBOX.AI is hard or impossible for you to use, we genuinely want to know — real reports are how the gaps above get found and fixed.
Email support@arcadebox.ai with:
- the page or feature you were using,
- what you expected and what actually happened, and
- the assistive technology or setting involved, if any (screen reader, keyboard only, magnification, reduced motion…).
We read every report. If you need something on this site in an alternative format, ask and we'll do our best to provide it.
6. If you're not happy with our answer
If you raise an accessibility problem with us and aren't satisfied with our response, you can use our complaints procedure. In the UK, the Equality and Human Rights Commission (EHRC) is responsible for enforcing accessibility-related equality law; in the EU, you can contact the market-surveillance authority in your member state.
7. Reviewing this statement
This statement was prepared on 1 August 2026, based on our own testing of the site and Studio. We review it when we ship significant interface changes, and at least once a year.
— The ARCADEBOX.AI team