MSRX Tools

Accessibility

What has been done, and — more usefully — what has not.

Last updated 28 August 2026

What has been done

  • Every control is reachable and operable with a keyboard, and the focus outline is always visible — it is never removed.
  • Colour is never the only way information is conveyed, and the brand cyan is never used for small text: it measures 2.4:1 on white and would fail. A darker tone carries the words.
  • Results announce themselves to screen readers as they appear, rather than changing silently.
  • Every input has a real label, and every icon-only button has a text alternative.
  • The interface respects your system's dark mode and your reduced-motion setting; with that setting on, animation is switched off rather than merely shortened.
  • Text reflows to a narrow window without a horizontal scrollbar, and can be zoomed without the layout breaking.

What has not been done

This is the part most accessibility statements leave out, so it is worth being direct.

This site has not been formally audited against WCAG 2.2, and no conformance level is claimed. It has not been tested with a screen reader by somebody who uses one daily, which is the only test that really counts.

Some tools ask for numbers where direct manipulation would be easier — the crop and blur tools take coordinates rather than offering a draggable box on the image. That works with a keyboard, which is why it was built that way first, but it asks more of everyone than it should.

File drag-and-drop has a keyboard-accessible alternative in every case, but the drop zone itself is not operable by keyboard.

If something does not work for you

Please write to mrinalsinghraja@gmail.com and say what you were trying to do, what got in the way, and what you were using. A specific report about one tool is far more useful than a general one, and it will be fixed rather than logged.