usefulweb.siteDependable little tools for people and AI agents.

Accessibility statement

Our commitment to WCAG 2.2 level AA, what we have done to make usefulweb accessible, known limitations and how to report barriers.

We want everyone to be able to use the tools on usefulweb.site, including people who use a screen reader, a keyboard, voice control, magnification or high-contrast settings. This statement covers usefulweb.site, all of its category, tool and app sites and the brand mirror usefulweb.app.

Our goal

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, level AA. The site is not formally audited by an external organisation; this statement is based on our own checks with automated tests, keyboard-only testing, screen-reader spot checks and browser tests at desktop and mobile widths. We consider the site partially conformant: most pages meet the target, the exceptions are listed below.

What we have done

  • Semantic HTML. Pages use real headings in a logical order, landmarks (header, navigation, main content, footer), lists, and tables with captions and header cells. Every page has a "Skip to content" link.
  • Forms. Every form field has a visible label; hints and error messages are connected to their fields, and an error summary at the top links to each field that needs attention.
  • Works without JavaScript. Tool forms are normal HTML forms: you can send them and get a result page without any scripts. JavaScript only adds conveniences such as a busy indicator.
  • Keyboard. All links, buttons and form controls can be reached and used with the keyboard, with a visible focus indicator. Code blocks and wide tables can be scrolled with the keyboard.
  • Colour and contrast. Text and interface elements are designed for sufficient contrast, and information is never shown by colour alone: status badges combine an icon and a word.
  • Status messages. Results and form status are announced to screen readers (live regions), and after a calculation the focus moves to the result heading.
  • Reduced motion. If your system asks for reduced motion, animations and transitions are switched off.
  • Zoom and small screens. Layouts adapt to narrow screens and to browser zoom; we check pages at a width of 320 CSS pixels (the same as 400 % zoom on a desktop screen) for content that would force horizontal scrolling.
  • Languages and right-to-left. The interface is available in 17 languages, every page declares its language, and Arabic is shown right-to-left.
  • Charts. Charts and graphs come with a table or text that contains the same data.

Known limitations

  • Light theme only on regular pages. The normal pages have a light colour scheme only; there is no dark theme yet. The premium-app workspaces offer both a light and a dark theme.
  • Premium-app canvases. Drawings, circuit wires, embroidery stitches and 3D scenes on the app canvases are not fully described for screen readers. Screen-reader users can work with the object trees and lists, the inspector panels and the result tables instead, and the tutorials and engine tools (normal tool forms and the API) are alternatives for many tasks.
  • Some canvas actions need a pointer. Drawing new geometry, freehand drawing, brushes and masks, and cropping by dragging need a mouse, pen or touch. Selecting, moving, nudging and editing existing objects and all numeric fields work with the keyboard.
  • Single-key shortcuts in the apps. The app workspaces use single-key shortcuts. You can switch them off in each app's shortcut sheet if they get in the way of speech input.
  • Flipline Story Desk not audited yet. Story Desk in Flipline is new and still in development; it has not been checked for accessibility yet.
  • Table rows after a failed submit. If a form with a table of inputs (rows you add yourself) is sent with an error, the table rows are not refilled. The error message names the cell that needs attention, so you can enter the rows again.
  • Native pickers. Date, file and selection fields use your browser's own pickers. How well they work with assistive technology depends on your browser.
  • Account menu. The account menu after signing in has not been tested with a screen reader yet.
  • Translations with AI assistance. Texts in languages other than English are translated with AI assistance and checked by automated tests. They may contain unclear wording, which can be a barrier for people who rely on plain language. The English version is the reference.
  • Third-party content. The consent dialog and advertisements are provided by Google. We cannot fully control their accessibility. Declining advertising does not limit any tool.
  • Complex results. Some technical explorers produce long tables and graphs. They are structured with headings and table headers, but can still be hard to navigate with a screen reader.

Report a barrier

If something on usefulweb is hard or impossible for you to use, please tell us. Use the feedback form (choose "Correction") or write to games@codemagic.net. Please name the page, what you tried to do and, if you like, the assistive technology you use. We will reply and, where possible, fix the problem or offer the information in another way. More ways to reach us are on the contact page.

About this statement

This statement was last reviewed on October 25, 2026. We update it when we fix a limitation or find a new one.

Last updated: