Accessibility Statement

Effective April 27, 2026 Last updated May 16, 2026 Version 1.0

Nova8 is committed to making its website and web application usable by as many people as possible, including people with disabilities. This statement describes our current accessibility posture, the standard we work to, and how to reach us if something is in your way.

1. Our standard

We work toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA, published by the W3C’s Web Accessibility Initiative. WCAG 2.1 AA is the standard most commonly referenced by accessibility laws including the US Americans with Disabilities Act (ADA), Section 508 of the Rehabilitation Act, the European Accessibility Act (Directive (EU) 2019/882), and the UK Equality Act 2010. Where WCAG 2.2 introduces additional success criteria that we can meet, we will adopt them.

2. What we do today

• Keyboard navigation. Every interactive element on the marketing site and in the dashboard is reachable and operable with the keyboard (Tab, Shift+Tab, Enter, Space, Esc, arrow keys for menus and lists). Focus is always visible.
• Screen-reader semantics. We use native HTML elements (<button>, <a>, <label>, <nav>, <main>) wherever possible, and add aria-* attributes only where native semantics are not enough. Custom widgets follow the WAI-ARIA Authoring Practices.
• Colour and contrast. We test text and meaningful UI controls against the 4.5:1 contrast ratio for normal text and 3:1 for large text. We support both light and dark modes and follow your operating-system preference by default.
• Reduced motion. We honour the prefers-reduced-motion media query and disable or shorten non-essential animation when it is set.
• Forms. Every form input has a programmatically associated label and a clear error message that is announced to assistive technology when validation fails.
• Images and icons. Decorative images use empty alt attributes; meaningful images carry a description; icon-only buttons carry an accessible name.
• Zoom and reflow. The marketing site and dashboard reflow at up to 400% zoom without loss of content or functionality.
• Per-project pages. The privacy and support pages we generate for the apps you build inherit the same baseline accessibility.

3. Known limitations

We are honest about where we are not yet fully conformant:

• The live mobile preview is rendered by an embedded simulator. Screen-reader access inside that preview reflects how your generated app would behave in a real device, not the dashboard chrome around it; that means some preview controls are not announced as fully as the rest of the app, and we are working to add explicit captions.
• Drag-and-drop interactions in the file tree currently expose keyboard equivalents, but they are still being polished — please reach out if you need a workaround.
• Some long-form output streamed from the build agent does not yet announce live-region updates to screen readers in real time. We are tracking this as a known issue.

We treat known accessibility issues with the same priority as functional bugs and aim to fix critical ones (anything that blocks a user from completing a core task) within 30 days of confirmation.

4. How we test

We combine automated checks (axe-core in CI), manual keyboard-only walk-throughs of the core flows (sign-in, project creation, build, preview, deploy, billing), and screen-reader spot-checks on VoiceOver (macOS / iOS) and NVDA (Windows). We do not yet engage an external accessibility audit; we plan to commission one once the platform reaches general availability.

5. Tell us when we get it wrong

If you encounter a barrier on Nova8 — on the marketing site, in the dashboard, in a per-project page, or anywhere else — please email [email protected] with the subject line Accessibility. Tell us:

• The page or screen where the issue occurs (a URL is best).
• What you were trying to do.
• The assistive technology you were using (if any) and your operating system / browser.
• What happened and what you expected to happen.

We acknowledge accessibility reports within 2 business days, and we will offer an alternative way to complete the task you were blocked on while we work on a fix.

6. Formal complaints

If you believe we have not adequately addressed an accessibility issue, you may have the right to file a complaint with the accessibility regulator in your jurisdiction (for example, the US Department of Justice under the ADA, or your national accessibility authority in the EU). We’d much rather hear from you first — but you do not need our permission to escalate.

7. Changes to this statement

The “Last updated” date at the top of this page reflects the most recent version. We will refresh this statement at least annually and any time the underlying conformance position changes materially.

8. Contact

Email [email protected] with the subject line Accessibility.