Company
Accessibility
A writing tool that some writers cannot use is not finished. DraftBloom is built to WCAG 2.2 level AA as a working target, checked automatically on every change, and this page says honestly where it stands.
Last updated September 20, 2026.
01What is in place
- Keyboard. Every control in the application is reachable and operable by keyboard, with a visible focus ring. The beat bar, sliders and version compare have arrow-key controls, and their instructions are on the page.
- Screen readers. Pages use landmarks and headings; buttons keep their names while they are busy; long-running work is announced through live regions; proposals are announced when they arrive.
- Contrast. Text in both the dark and the light theme meets 4.5:1 against its surface; the smallest labels are checked at 3:1 or better. The two themes are a choice on every page and follow your system by default.
- Motion. Animation respects prefers-reduced-motion; the landing page’s scroll film is still under your control.
- Zoom and phones. Every page works at 200% zoom and at 390px wide without sideways scrolling.
- Testing. Automated accessibility checks (axe) run in the end-to-end suite on every stage of the product before a release.
02What is not there yet
- The prose editor is a contenteditable region; it is usable with a screen reader but does not yet announce paragraph provenance (yours or the model’s) as you move through it.
- Drag-and-drop reordering of beats and scenes has a keyboard equivalent, but the drag itself does not announce its progress.
- Exports (ePub, Word, PDF) carry the book’s headings; alt text for pinned sketches is generated from the character’s name and can be edited only by replacing the picture.
These are on the list, in that order.
03Tell us
If something on DraftBloom does not work with your assistive technology, email support@draftbloom.com with the page and what you use. Accessibility reports are read first and fixed ahead of ordinary bugs.