Saturn
accessibility

Accessibility statement.

What we support, what we don’t yet, and how to flag a barrier.

Last updated

Our commitment

Saturn is built for makers. We treat accessibility as a craft requirement, not a checkbox: if a person who relies on a screen reader, keyboard navigation, or high contrast can't ship from the same surface as anyone else, we haven't finished the work.

We aim to meet WCAG 2.2 Level AA across the entire public marketing surface and the authenticated product UI. Where we fall short of that bar today, we say so on this page rather than hiding behind a conformance claim.

Conformance status

Saturn targets WCAG 2.2 Level AA. As of the date below, the marketing surface (homepage, pricing, security, privacy, terms, the comparison and alternative-to landings) substantially conforms — semantic landmarks, keyboard-reachable interactive elements, visible focus rings, sufficient color contrast on text, and a 'skip to main' link on every page.

The product UI (Make, Manage, Discover) is in active hardening. Some interactive surfaces — autopilot step viewers, drag-reorder, in-canvas previews — are still being audited against the screen-reader and keyboard-only flows. We don't claim full AA on the product UI yet.

What we support today

These behaviors hold across the marketing surface and the core product flows:

  • Keyboard navigation. Tab, Shift+Tab, Enter, Space, Esc, and arrow keys behave the way a keyboard user expects across menus, modals, and form controls.
  • Visible focus. Every focusable element renders a visible focus ring in Saturn's brand gold — never removed via outline:none alone, never invisible against the dark canvas.
  • Semantic markup. Headings cascade in document order. Landmarks (header, nav, main, footer) carry aria-labels where multiple instances exist on a page.
  • Color contrast. Body text on the dark canvas (#000) clears AA against #ededed for primary, #a1a1a1 for secondary, and #8a8a8a for dim. Buttons and links retain contrast in their focus and hover states.
  • Reduced motion. The brand's ambient flourishes (orbit backdrops, shooting stars, marquees) honor prefers-reduced-motion and degrade to static or paused states.
  • Form labels. Every input has an associated label. Error messages are linked via aria-describedby. Submit buttons announce their state when busy.
  • Live regions. Plan and Build streams announce progress to assistive tech via aria-live polite. The status page exposes service health as text, not just color.

Known limitations

We're being explicit about the gaps so you can plan around them and so we can close them. As of the date below:

  • Discover canvas. The trending project canvas uses drag-reorder for staff curation; keyboard equivalents are partial. Read-only browsing is fully accessible.
  • Autopilot step viewer. The Build stage's run timeline renders nested step trees; screen-reader navigation between siblings is workable but verbose. We're shipping a flatter announcement model in the next release.
  • Custom-domain manage. Some inline forms in Manage → Settings → Domain don't yet expose validation errors via aria-describedby; errors are visible but may not be announced. Workaround: validate against the site's instructions before submitting.
  • Brand video on /demo. The 78-second demo has no audio narration today (it's a silent screen capture); captions are not yet attached. A captioned version is on the roadmap.

Browser and assistive-tech compatibility

Saturn is tested on the latest two stable releases of Chrome, Safari, Firefox, and Edge. Screen-reader testing covers VoiceOver on macOS and iOS, NVDA on Windows, and TalkBack on Android. We don't intentionally drop support for older versions, but we don't gate releases on them.

If you rely on a configuration we haven't tested and something is broken, write us — we'll triage and most of the time we can fix it.

Report an issue

If you encounter a barrier on Saturn, tell us. Email support@saturnos.app with the URL, the action you were trying to take, and the assistive technology you're using. We aim to acknowledge within two business days and to ship a fix on the next deploy where the change is straightforward, or to give you a timeline where it isn't.

We don't run a paid bug-bounty program for accessibility issues, but we credit reporters by name (or handle) in the changelog if they want recognition.

Review cadence

This statement is reviewed quarterly and after any material change to the public surface or the product UI. The 'last updated' date below reflects the most recent review.

Companion documents: Security · Privacy · Contact.