Accessibility Statement

1. Our commitment

WriteFlow aims to be usable by everyone, including people who use screen readers, keyboards-only navigation, magnification, or voice control. We target WCAG 2.1 Level AA and treat accessibility bugs as product bugs.

2. What we do today

• Semantic HTML with labelled landmarks and a logical heading order.
• Every interactive control is reachable and operable by keyboard, with focus styles that stay visible.
• Form fields have persistent labels, and errors are shown as text next to the field — never by colour alone.
• Meaningful images carry alt text; decorative images are marked decorative.
• Layouts reflow down to small screens; text can be zoomed without losing content.
• Animations respect your system’s reduced-motion setting where the platform allows it.
• We run automated accessibility checks as part of QA and manually test key flows (sign-in, reading, writing, publishing, billing).

3. Known limitations

• Some embedded third-party videos may lack captions, and reader comments are authored by users, so their structure varies.
• Alt text for images inside articles depends on what the author supplies.
• Some older PDF-style or rich embeds inside third-party content may not be fully navigable by screen reader.

We are actively working to reduce these limitations.

4. Conformance status

WriteFlow is partially conformant with WCAG 2.1 Level AA. The core flows — browsing, reading, writing, publishing, and managing an account — are designed to meet AA; the exceptions are the limitations listed above.

5. Feedback and alternatives

Hit a barrier? Tell us at support@getwriteflow.com with the page address and what went wrong. We aim to respond within 5 business days. If you need any content in an alternative format, ask and we will provide it.

6. Review

This statement is reviewed when we ship significant UI changes and at least annually. See also our Privacy Policy and Terms of Service.