Trust & Governance · Last updated June 2026
Accessibility Statement
Writing well is an act of consideration. Accessibility is the same act, applied to software. We design RewriteAIForMe so that more people can use it on their own terms.
The standard we aim for
We design and test against the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. This standard covers perceivability, operability, understandability, and robustness across keyboard, screen-reader, and assistive-technology users.
What we build for
- Full keyboard operability across navigation, the editor, and the rewrite surface.
- Visible focus styles on every interactive element.
- Semantic landmarks, headings, and ARIA labels for screen-reader users.
- Colour contrast that meets or exceeds 4.5:1 for body text and 3:1 for large text and UI components.
- Motion that respects the operating system's reduced-motion preference.
- Text that scales without breaking layout when zoomed up to 200%.
Known limitations
Accessibility is a practice, not a finished state. We are still improving keyboard shortcuts inside the rewrite canvas, the announcement pattern for asynchronous output, and the contrast on a small number of secondary surfaces. We treat these as defects rather than as accepted gaps.
Reporting a barrier
If something on the site or in the product stops you from doing what you came to do, we want to hear about it. Describe what happened, the page or feature, and the assistive technology you were using. We aim to respond within five business days and to ship a fix or a workable plan within thirty.