Accessibility Statement

Accessibility is part of how we design and build StoryHelm, not an afterthought. The practices below are woven through the product.

• Keyboard navigability. Core flows, including upload, navigation, analysis results, and the editor, can be operated without a mouse. Interactive controls are reachable and usable with the Tab, Enter, and Escape keys.
• Visible focus states. We keep a clear, visible focus indicator on interactive elements so you always know where you are on the page, and we do not remove it.
• Color and contrast. We aim for text contrast that meets WCAG AA, and we avoid using color as the only way to convey meaning. Status and severity are also signaled with icons, labels, and text.
• Semantic structure. We use meaningful headings, landmarks, labels, and ARIA attributes so that screen readers and other assistive technologies can present the page in a logical order.
• Dark mode. StoryHelm offers a calm, high-contrast dark theme alongside the light theme, so you can read and write in the setting that is easiest on your eyes.
• Responsive layouts. The interface adapts to different screen sizes and supports zoom and larger text, so you can work comfortably on the device you prefer.

We would rather be honest than overstate where we are. StoryHelm includes some rich, data-dense visualizations, such as timelines, the analysis pipeline, canon graphs, and tension and pacing curves. These give a powerful at-a-glance read on a manuscript, and they are also the hardest parts of the product to make fully accessible.

Some of these complex visualizations may not yet expose every detail to screen readers or be fully operable by keyboard. Where that is the case, we work to provide the same information in an accessible form, such as text summaries, tables, and findings lists, and we are actively improving the visualizations themselves. If a particular view is getting in your way, please tell us. Your report helps us prioritize the fixes that matter most.

If you run into an accessibility barrier anywhere in StoryHelm, or you need information in an alternative format, we want to hear from you. Email support@storyhelm.com and let us know the page or feature involved, what you were trying to do, and the assistive technology, browser, or device you were using. The more detail you can share, the faster we can help.

We aim to respond promptly, and we will work with you to find a path forward, whether that means a workaround, an alternative format, or a fix in the product. You can also reach our team through the contacts on our Security and Privacy pages for related questions.

Accessibility is never finished, and we treat it as a continuing commitment. We review new features against WCAG 2.1 AA as we build them, fold accessibility checks into our design and testing, and revisit older parts of the product as we go.

The feedback authors send us is one of the most valuable inputs to this work. As we make meaningful progress, we will update this statement so you can see how StoryHelm is getting more usable for everyone. Thank you for helping us build a writing companion that welcomes every author.