Last reviewed: October 24, 2026

Our commitment

We are committed to making Galleon accessible to people with disabilities. This commitment covers the Galleon website, the core platform, and the built-in applications that we provide with the platform. We aim to provide an inclusive experience that allows people to access information and use Galleon's features regardless of their abilities or the assistive technologies they use.

We also aim to make it convenient for third-party developers to build ADA-compliant applications for the platform's applications layer.

We continue to evaluate and improve the accessibility of the website, the core platform and the built-in applications.

Accessibility standard

Our accessibility efforts are guided by the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA.

Current accessibility status: We have reviewed the main public pages of this website (the home page, and the about, download, sign-in, agreement and privacy pages) against this standard, and fixed the problems we found. This work is ongoing.

What we check

We are currently making our best effort to address each of the following areas and types of issue. This work covers both this website and the Galleon platform environment. The platform environment has two parts: the core platform, which we build, and an applications layer, which is made up of the built-in applications we provide and, in the future, third-party applications that run in the environment.

Text and color

  • Text has enough contrast against its background, in every state: normal, hovered, focused and selected.
  • Icons, input borders, focus outlines and other visual signals have enough contrast to be seen.
  • Color is never the only way information is shown; it is paired with text, an icon, an underline or a shape.
  • Pages still work when zoomed to 200%, and fit a narrow, phone-width window without sideways scrolling.
  • Text spacing (line height, letter and word spacing) can be increased without text being cut off or overlapping.
  • Pages never block zooming.

Images and media

  • Meaningful images have text alternatives that say what they show or do.
  • Purely decorative images are hidden from screen readers.
  • Pictures of text are avoided, or their text alternative repeats the text.
  • Complex images, such as charts and diagrams, have a longer description nearby.

Keyboard

  • Everything that can be clicked can also be reached with the Tab key and used with Enter (and Space, for buttons).
  • The Tab order follows the visual reading order.
  • A visible outline shows where keyboard focus is.
  • Keyboard focus is never trapped; Tab and Shift+Tab can always move on.
  • Page scripts do not block the keys that people use to navigate.
  • Single-key shortcuts can be turned off or changed, or only work when a control has focus.
  • Pages with long, repeated navigation offer a way to skip past it, such as page landmarks.

Structure and meaning

  • Each page declares its language.
  • Each page has a unique, descriptive title.
  • Headings form a logical outline.
  • Page regions are marked as header, navigation, main content and footer.
  • Lists, tables and forms use real HTML elements.
  • Standard HTML controls are used wherever possible, with ARIA added only where no standard control fits.
  • Custom controls report their role and state (such as selected or expanded) to assistive technology.
  • Every control has a name that a screen reader can announce.
  • Element identifiers are not duplicated within a page.

Links and navigation

  • Link text makes sense on its own, without relying on "click here" or "more".
  • Links that open a new window or a file, such as a download, say so.
  • Navigation is consistent from page to page.
  • There is more than one way to find a page, such as the menu and the footer links.

Forms

  • Every input has a visible label that is tied to it.
  • Errors are described in text, next to the field, and announced to screen readers.
  • Suggestions for fixing an error are given when known.
  • Personal-information fields, such as email, can be filled in automatically by the browser.
  • Nothing changes unexpectedly just because a field receives focus or its value changes.

Motion and timing

  • Anything that moves, blinks or updates automatically for more than five seconds can be paused, stopped or hidden.
  • Nothing flashes more than three times a second.
  • Time limits can be turned off, adjusted or extended.
  • Audio that plays automatically can be stopped or turned down.

Changing content

  • Status messages are announced to screen readers without moving keyboard focus.
  • When content is shown or hidden, keyboard focus goes somewhere sensible.
  • Pop-ups and dialogs receive focus when they open, close with the Escape key, and return focus to whatever opened them.
  • Content that appears on hover or focus can be dismissed, and stays in place while the pointer is over it.

Documents (PDF)

  • PDF documents are tagged, so assistive technology can follow their structure and reading order.
  • Page headers, footers and page numbers are marked so screen readers can skip them.
  • Headings, lists and tables in PDFs use proper structure, and figures have text alternatives.
  • Each PDF declares its language and shows a meaningful title.
  • Fonts are embedded so text can be copied and read aloud.
  • Longer documents include bookmarks.
  • The same contrast rules apply as on web pages, and PDFs are checked with an accessibility validator.

Video and audio

  • Videos have synchronized captions for speech and meaningful sounds.
  • Important visual information that is not spoken is described, in audio or in text.
  • Audio-only content has a transcript.
  • Media player controls can be used with the keyboard and are labeled.
  • Media does not play automatically, or starts muted with an obvious pause control.

Special instructions for NVDA users

NVDA starts out in browse mode, which is the best way to survey a page or a newly drawn view: you can read it line by line and jump between headings, links and landmarks. Once you have surveyed the page or view and want to work with it, switch to focus mode, so that your keystrokes go to the page and its controls instead of to NVDA.

  • Press NVDA+Space to switch between browse mode and focus mode. The NVDA key is Insert by default, so this is usually Insert+Space.
  • A high-pitched beep, along with a typewriter sound, means you are now in focus mode.
  • A somewhat lower-pitched sound means you are back in browse mode.

Known site limitations

We have not yet completed a full evaluation of every part of Galleon, so some barriers may remain.

Known issues:

  • When using the NVDA screen reader, moving through the items of the "More" menu at the top of the page with the Up and Down arrow keys reads each item correctly, but the visible focus ring is not shown on the item being read. Navigation still works: each item can be chosen with Enter as usual. To see the focus ring, press Tab, or switch NVDA to focus mode (NVDA+Space) before using the arrow keys.

We welcome reports of accessibility problems and will make reasonable efforts to address them.

Known applications layer limitations

The applications layer of the platform environment will host applications made by third parties. We do not guarantee, and do not take responsibility for, the usability of these third-party applications.

If you find an accessibility problem in a third-party application, you are still welcome to report it to us as described below. We will pass it on to the application's developer where we can.

Reporting a problem or requesting an accommodation

If you have difficulty using any part of this website, please email us at support@unitraverse.com and put the word ACCESSIBILITY in the subject line.

In your message, please clearly describe the issue that needs attention, or the accommodation you are seeking, including the page or feature you were using. You may also tell us which browser or assistive technology you were using, if you are comfortable sharing that information.

If you cannot access particular information or functionality, please contact us so that we can discuss an alternative way to provide it.

Assessment and ongoing improvement

We check this website with a combination of methods, because automated tools catch only some problems:

  • Automated scans with an accessibility checker, with suspicious colors measured directly.
  • Keyboard-only walkthroughs of each page.
  • Screen-reader checks of headings, landmarks and form labels.
  • Viewing pages zoomed to 200% and at phone width.
  • Re-testing the live site after each change is published.

We review accessibility as the website evolves, and update this statement when material changes occur.