Skip to main content

Accessibility Statement

Last reviewed: 2026-09-09

Our commitment

Device Cortex, LLC builds NovaXplora. We want it to work for people who browse with a keyboard only, a screen reader, screen magnification, speech input, or a high-contrast or reduced-motion setting.

Our target is WCAG 2.2 Level AA. That is the Web Content Accessibility Guidelines published by the W3C, at the middle of their three levels.

We are working through the site area by area. So far that work has covered:

  • Colours and spacing, so text and controls have enough contrast in every theme.
  • Shared building blocks: dialogs that move focus and hold it, menus that respond to the arrow keys and Escape, and form fields that are properly labelled.
  • The signed-in app: its navigation, headings, landmarks and skip link.
  • The public site and the shared-plan gallery.
  • The admin area.
  • The trip-planning tools.
  • The sign-in and registration screens.

Not all of that work is finished. The next section says where we actually stand.

Part of the checking is automatic: colour contrast is calculated from our design tokens on every change, so a colour that falls below the standard fails the build instead of reaching you. The browser-level scans described further down are run against a working copy of the site rather than on every change.

Conformance status

NovaXplora is partially conformant with WCAG 2.2 Level AA. Partially conformant means most of the site meets the standard, but some parts do not, and some parts have not been checked thoroughly enough for us to claim they do.

We track the remaining work in public. It is gathered under issue #368 (opens in a new tab) on our issue tracker, along with the individual tickets under it.

Known limitations

We would rather tell you what does not work than let you find it:

  • Screen readers have not been tested by hand. We have not yet done a full manual pass with VoiceOver and Safari, or with NVDA and Chrome. Automated tools and keyboard testing cannot catch what those passes catch — a confusing reading order, a label that makes no sense out of context, a status message that is never announced. Both passes are planned. Until they are done, treat screen-reader support as untested rather than confirmed, and please tell us what you hit.
  • Our automated checks cover a sample, not everything. They run over the public pages, a set of signed-in pages and the admin pages, at two window widths. Screens outside that sample have not been scanned; for those we rely on reading the code.
  • Some content comes from other companies. Map tiles and provider-supplied place details are not under our control and may not meet the same standard. Where that blocks a task, tell us and we will look for another way to give you the same information.
  • JavaScript is required. NovaXplora does not work with scripting turned off.

Report a barrier

If something on NovaXplora blocks you, tell us. We treat it as a defect, not as a feature request.

  • Email [email protected]. Putting the word Accessibility in the subject line gets it to the right person faster.
  • If you are signed in, use the Send Feedback button in the top bar of the app.

It helps if you can tell us the page address, what you were trying to do, and what you were using — browser, operating system, and any assistive technology.

We aim to reply within 5 business days. If a fix will take longer than that, we will say what we are doing instead and when we expect it to be done.

Compatibility with browsers and assistive technology

NovaXplora has been tested with:

  • Current Chrome and other Chromium browsers, using a keyboard only, at a desktop window width and at a phone width.
  • Automated WCAG 2.2 AA checks in the same browser.

It has not been tested with:

  • Any screen reader, by hand. See Known limitations above — this is the gap we are most aware of.
  • Speech-input software, switch access, or braille displays.
  • Firefox and Safari beyond routine use. The site is built to web standards and should behave the same way in both, but the results reported here come from Chromium.

NovaXplora needs an up-to-date browser.

Technical specifications

Accessibility on NovaXplora depends on these technologies working together with your browser and any assistive technology you use:

  • HTML
  • WAI-ARIA
  • CSS
  • JavaScript

If one of these is unavailable or turned off, parts of the site will not work.

How we assessed this site

By self-evaluation. Device Cortex carried out the assessment itself; we have not commissioned an outside audit, and this statement is not a VPAT or an Accessibility Conformance Report.

What the self-evaluation consisted of:

  • Automated scans with axe-core 4.12.0, driven by Playwright in Chromium, across the public pages, a set of signed-in pages and the admin pages, at a desktop width of 1280 pixels and at an iPhone 14 width of 390 pixels.
  • Keyboard walks through the tab order, checking that every stop shows a visible focus indicator and that no fixed header or footer covers the control that has focus.
  • Colour-contrast ratios calculated directly from the design tokens in a test, so a colour change that breaks contrast fails the build instead of shipping.
  • Review of the interface code by hand.

Date of this review: 2026-09-09.

Formal complaints

Please contact us first — see Report a barrier above. We would rather fix the problem than argue about it.

If you are not satisfied with our response, you can raise it with the Civil Rights Division of the US Department of Justice, which enforces the Americans with Disabilities Act: File a Complaint (ada.gov) (opens in a new tab).