Accessibility Statement

Last reviewed: August 2026

Our Commitment

Cosyslabs is committed to ensuring Dev Tools ! is accessible to the widest possible audience, including people with disabilities. We aim to conform to WCAG 2.1 Level AA across all pages and tools.

Measures We Take

  • Semantic HTML5 landmarks and proper heading hierarchy.
  • Interactive elements are reachable and operable with the keyboard.
  • Focus indicators are clearly visible (2px accent outline).
  • Every form control in the tools is named — either by a <label> tied to it with htmlFor, or by an aria-label — so a screen reader announces what the field is for rather than just “edit text”.
  • Decorative icons and emoji are marked aria-hidden so they are not read out. The interface is built from text and inline SVG rather than images, so there is very little alt text to get wrong.
  • Body text and secondary text meet the WCAG AA contrast minimum of 4.5:1 against their background. One exception is listed under Known Limitations below.
  • Respects prefers-reduced-motion for animations.
  • Live regions (aria-live) announce status messages such as form results, consent changes and assistant replies.
  • Skip-to-content link at the top of every page.

Known Limitations

We would rather name these than let the list above imply the site is finished. Each one is a real gap we have measured and intend to close.

  • One text colour falls short of AA. The lightest of our three text colours — used for line numbers, character counts and similar secondary detail — measures about 2.8:1 against the page background in light mode and 3.4:1 in dark, below the 4.5:1 AA minimum. Re-tuning it is queued.
  • One control outside the tools is still unnamed. The box for naming a saved flow on the Flows page is labelled only by its placeholder text, which most screen readers do not treat as a name.
  • Most tools do not announce their results. A handful use a live region, but in the majority a screen-reader user has to move to the output field to read the result or the error rather than hearing it announced.
  • The Single / Batch / History tabs on each tool can be reached with Tab, but do not yet support arrow-key navigation, and the panels are not programmatically linked to their tabs.
  • Some emoji placed next to button text are still read aloud — for example the clipboard emoji before “Copy”.
  • Some third-party widgets (ads, analytics scripts) may not be fully accessible.
  • PDF downloads are not yet screen-reader optimised.
  • Complex visualisations (color pickers, canvas-based tools) are progressively enhanced.

Feedback & Contact

If you encounter an accessibility barrier on any page, please contact us. We aim to respond within 5 business days.

Email: support.cosyslabs@gmail.com

Enforcement

If you are not satisfied with our response, you may contact the relevant enforcement body in your jurisdiction. In the EU, this is typically your national equality or disability rights authority.