Accessibility
What works, and what does not yet.
We aim at WCAG 2.1 AA. Some of it is done and tested, some of it is not done yet, and this page says which is which rather than claiming the whole thing.
Last updated 12 August 2026
What is built in
These are properties of how the site is built rather than features added on top, which is why they hold on every page rather than the ones somebody remembered.
- Every page is real server-rendered HTML with one h1, headings in order, and landmarks — a test fails the build if any route has more or fewer than one h1.
- Colour is never the only signal. The QR correctness comparison labels its two sides “Wrong” and “Right” in words, and the tick columns on the home page carry a screen-reader-only “Yes” or “No” beside the glyph.
- Colour pairs are checked by computation, not by eye. The contrast of every accent against its text is asserted in a unit test, and a choice that cannot reach 4.5:1 in both light and dark is refused rather than shipped.
- Motion respects prefers-reduced-motion in two layers — CSS for keyframes, JavaScript for the animation library — and a test asserts nothing on the site animates infinitely.
- Content is never hidden behind an animation. Everything ships visible in the HTML and motion is added afterwards, so a reader with JavaScript off or a crawler that runs none still gets the whole page.
- The tools work with the keyboard: Escape backs out one layer at a time in the note editor, the split-pane divider moves with the arrow keys, Home and End jump it to either end, and [ and ] step between tools in a family without stealing those characters while you are typing.
Known gaps
These are real and currently unfixed. They are listed because you are more likely to hit one than to read a promise about it, and because naming them is what makes the list above worth anything.
- The QR generator's form fields show focus as a border colour change rather than a visible ring, which is weaker than the ring every other control on the site gets. This is being fixed.
- Some controls in the print studio and the PDF page organiser are icon-only, with their meaning carried in a tooltip a touch device cannot reach.
- The print studio's canvas is drag-only: moving, resizing and rotating an element on the page has no keyboard or numeric equivalent yet. Every other tool that offers dragging also offers a field or a slider.
- Form fields that fail validation announce their error text but do not yet mark themselves invalid programmatically.
Telling us
If something here is unusable with the assistive technology you use, that is a bug and we want it. Say what you were trying to do, what happened, and what you were using — the browser, the platform, and the screen reader or input method if that is relevant. Write to contact@cloudexistechnologies.com.
There is no separate accessibility queue and no ticket number: it is the same address as everything else, read by the people who wrote the code.