Skip to content
WriteSignal
Template — pending review. This document is a working draft that describes how WriteSignal currently handles data. Confirm your legal entity name, jurisdiction and contact addresses, and have counsel review it before relying on it in a customer contract.

Accessibility Statement

Last updated: September 3, 2026

WriteSignal is committed to being usable by everyone, including people who rely on assistive technology. We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA.

Conformance status

The core product substantially conforms to WCAG 2.1 AA. We audit the application with automated tooling (axe-core) alongside manual review, and we treat accessibility defects as bugs. This statement is updated as the product changes.

What we've built for accessibility

Specific measures currently in place include:

  • Full keyboard operability, a visible focus indicator, and a “skip to content” link.
  • Semantic landmarks and headings, and accessible names on controls (including icon-only buttons).
  • Labels tied to every form field, with appropriate autocomplete.
  • Colour is never the only signal — warnings and states pair colour with an icon and text.
  • A light and dark theme, both meeting AA contrast, plus respect for the OS setting and a manual toggle.
  • Respect for prefers-reduced-motion: animations and transitions are minimised for users who ask for it.
  • A responsive layout that works down to small mobile screens.
  • The editor is a standard, labelled text field; its visual highlight layer is hidden from assistive technology.

Known limitations

We're candid about what still needs work: a formal third-party WCAG audit and a published VPAT are on our roadmap, the rich-text highlight editor would benefit from further testing with a range of screen readers and input-method editors, and the interface is currently English-only. If any of these blocks your use, tell us and we will prioritise it.

Feedback & contact

If you encounter an accessibility barrier, please contact [accessibility@your-domain] with the page, what you were trying to do, and the assistive technology you were using. We aim to acknowledge reports promptly and will work with you on an accessible alternative in the meantime.