Accessibility at Nova

1. Standards we target

Nova targets conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, the standard referenced by the U.S. Department of Justice for ADA Title III public accommodations, the European Accessibility Act (EAA), and Section 508 of the U.S. Rehabilitation Act.

Our self-assessment is ongoing. A formal independent audit is queued; this page will be updated with the audit findings, remediation plan, and Voluntary Product Accessibility Template (VPAT) when complete.

2. What works today

• Keyboard navigation across primary surfaces (chat, memory, horizon, profile).
• Skip-to-content link at the top of every page for screen-reader and keyboard users.
• Semantic HTML landmarks (header, main, nav) to support assistive-technology navigation.
• Visible focus states on interactive elements.
• Transcripts for voice interactions (Riff) appear in the same chat thread, accessible to text-only readers.
• Image attachments support alternative-text fallbacks where the user provides them.
• Color is never the sole means of conveying information.
• Site language declared (lang="en") at the document root.

3. Known limitations

We are honest about where Nova still has gaps. Active items:

• Animated elements: the Memory tab, NovaThinking stardust, and Constellation surfaces use motion. We respect prefers-reduced-motionon the most prominent surfaces and are extending coverage. If motion causes you discomfort, please contact us — we will help.
• Color contrast: some secondary text intentionally uses lower contrast to recede. We are auditing and correcting where ratios drop below WCAG AA (4.5:1 normal, 3:1 large).
• Voice mode (Riff):Riff is bidirectional speech. Users without microphone access can use text chat for the same conversations — voice is never required.
• Image generation output: AI-generated images do not yet auto-produce alt text. Users may add descriptions before saving to memory.
• Third-party content: some integrations (e.g., calendar event detail rendered from Google sources) inherit the source's accessibility quality. We surface fallback text where possible.

4. Assistive technology compatibility

Nova is tested against:

• VoiceOver (macOS, iOS) on Safari and Chrome.
• NVDA on Windows + Chrome and Firefox.
• TalkBack on Android Chrome.
• Standard browser zoom up to 200% without horizontal scrolling.

If you use other assistive technology and encounter problems, please tell us so we can broaden our compatibility coverage.

5. Report a barrier

If something in Nova is unusable for you because of a disability, please email accessibility@novasystems.app with:

• The page or surface where the barrier appears.
• What you were trying to do.
• What assistive technology, browser, and device you are using.
• Any error message you saw.

We aim to acknowledge accessibility reports within five business days and to provide a remediation plan or workaround within thirty days. Critical barriers (a feature is impossible to use with assistive technology) move to the front of the line.

6. Formal complaint

If our response does not resolve your concern, you may also contact:

• United States:U.S. Department of Justice Civil Rights Division — ADA Information Line (800) 514-0301 or ada.gov/file-a-complaint.
• European Union: the equivalent enforcement body for the European Accessibility Act in your country of residence.
• United Kingdom: the Equality Advisory and Support Service.

7. Continuous improvement

Accessibility is not a checkbox — it is a posture. Every time we ship a feature, we ask: who could be locked out of this? When we miss something, we name it and fix it. This page will be updated whenever our posture changes, with a new effective date.

8. Related

See also our Privacy Policy, Security, and Terms of Service.