Accessibility
What we have done, what we know is still hard, and how to tell us about a barrier.
Last updated: 16 October 2026
This page is not finished. The operator details —
legal or trading name, contact email and country — have not been
filled in. Set them in tools.manifest.json under
site.operator before this site goes live or is submitted
for ad review. Deliberately left blank rather than guessed at.
Our aim
We aim for the tools and pages to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. The site has not been through a formal third-party accessibility audit, so we do not claim conformance. What follows is what is in place and what is known to fall short.
What is in place
- A skip link at the top of every page to jump past the navigation.
- Pages use headings in order, landmarks (header, main, navigation, footer) and descriptive link text.
- Form controls have visible labels, and in most tools the result is placed in a live region so a screen reader announces it.
- Everything that can be done with a mouse can be done with the keyboard, with a visible focus ring.
- A dark and a light theme, following your system setting unless you choose one.
- Animation is reduced or removed when your system asks for reduced motion.
- Data tables use header cells, and wide tables scroll sideways instead of being cut off.
- The layout reflows on small screens and when text is enlarged, without horizontal scrolling of the page.
- The tools work without an account, a sign-in or a time limit, and most work offline once loaded.
Known limitations
- Pointer-based tools. Tools that are drawn by dragging, such as the drawing pad, image cropper, screenshot annotation and some chart and layout makers, depend on a mouse or touch. Where we can we provide numeric fields as an alternative, but not every one has a full keyboard route yet.
- Hardware tests. Tests that rely on seeing a colour, hearing a tone or watching a pixel, such as the dead pixel test, speaker test and colour-blindness simulator, are visual or audio by nature.
- Generated files. Images, PDFs and other files you create are only as accessible as their content. A generated PDF will not have tagged structure or alternative text unless the tool says so.
- Third-party content. Advertising, when shown, is supplied by another company and we do not control its accessibility.
Browsers and assistive technology
The site is designed for current versions of Chrome, Edge, Firefox and Safari on desktop and mobile. We have not tested against every combination of browser and screen reader, and results may vary.
Tell us about a barrier
If something is hard or impossible to use, please tell us through the contact page. Name the page, say what you were trying to do, and what browser and assistive technology you use if you are happy to. We treat these reports as bugs and fix them in the same way as an incorrect result.
Contacting us
Operator name, contact address and email have not yet been set for this site. See the contact page.