AgentWrite

Accessibility

How we approach accessibility at AgentWrite, what we build for, where we know we fall short, and how to tell us when something gets in your way.

Last updated August 19, 2026

1. What we're aiming for

AgentWrite is used by working agents, and the people doing that work have a wide range of sight, hearing, movement, and attention. We build for that on purpose rather than as an afterthought.

We work towards WCAG 2.2 Level AA on our public pages as a goal we measure against. It is a goal, not a finished state: nobody has audited this site, we hold no certification, and we're not going to tell you we're “fully compliant” when no one has checked.

2. What that means in practice

The things we actually build and check for:

  • Contrast — text and interface colours are checked against their real backgrounds in both the light and dark themes, not just the one we happen to be working in.
  • Labelled fields — every input has a label a screen reader can announce, and errors are tied to the field they belong to rather than floating loose at the top of a form.
  • Keyboard access — the app is navigable without a mouse, focus moves somewhere sensible when a dialog opens or closes, and focus outlines are left visible rather than styled away.
  • Structure — headings describe the page rather than decorate it, lists are lists, and buttons are buttons.
  • Motion — if your system asks for reduced motion, the app stops animating scroll and moves you straight to where you asked to go.
  • Reading comfort — long-form text keeps a readable size and line length, and the app works when you zoom in or make text larger.

3. Where we know we're behind

Being honest about this is more useful to you than a clean-sounding page:

  • The screens behind the login have had less scrutiny than the public ones. They are where the work is, and they're improving as we go.
  • We test with keyboard navigation and contrast measurement routinely. We have not run a full audit with every major screen reader, so there will be things we haven't found.
  • Some content isn't ours. Copy the AI writes for you, and articles on our blog, don't go through the same checks the interface does.

4. Tell us what's broken

If something here gets in your way, we want to hear about it — a report about a real barrier is worth more to us than any checklist.

Email support@agentwrite.app and, if you can, tell us:

  • The address of the page you were on.
  • What you were trying to do, and what happened instead.
  • What you were using — browser, and any screen reader or other assistive technology.

A person reads these. We'll reply, and we'll fix what materially stops you working as quickly as we reasonably can. If something will take us a while, we'll say so rather than go quiet, and we'll try to suggest another way through in the meantime.

5. Related

Our Privacy Policy covers what we do with your information, and our Terms of Service cover the rest of the agreement.

Accessibility · AgentWrite