Accessibility Statement

We build Olto Discovery to be usable by the widest possible group of researchers, including people with disabilities. Our target is WCAG 2.1 Level AA, and we treat it as an ongoing engineering responsibility, not a one-time pass before launch.

We design and build against WCAG 2.1 Level AA: semantic structure (headings, landmarks, lists), text alternatives for non-decorative images, sufficient color contrast in both themes, visible keyboard focus, screen-reader support via ARIA where it helps, and keyboard operability for interactive controls (some complex controls, such as the drag-and-drop designer, remain a work in progress).

Primary nav items, forms, menus, and controls are designed to be operable with a keyboard alone. A “Skip to main content” link is provided as the first focusable element on our pages. Modals and dropdowns are built to close on Escape, and forms expose accessible names and validation messages.

Pages use HTML5 landmarks (header, nav, main, footer) and a logical heading order. We label icon-only buttons with an aria-label or visually-hidden text, and mark decorative graphics with alt="" or aria-hidden so they don’t interrupt the reading order. Status changes — toasts, error messages — use ARIA roles where appropriate.

Olto Discovery ships light and dark themes, plus eight accent color-ways, designed to target WCAG 2.1 AA contrast for normal and large text. We respect prefers-reduced-motion at the OS level: with it on, transitions and animation are minimized or turned off in the areas we control.

Interactive controls on small screens are sized to roughly 44×44 CSS pixels for accurate touch input. Most layouts reflow from mobile to desktop without horizontal scrolling at standard zoom levels; some data-dense views (large tables, the step designer) scroll within their own container.

Some embedded elements — hCaptcha, Stripe checkout, payment iframes — come from outside vendors. We chose ones that publish their own accessibility commitments, but we don’t control the markup inside those embeds. If one of them blocks you, tell us; we’ll look for a workaround or a different vendor.

Olto Discovery is under active development. Some areas may not yet fully match our target conformance level — the snapshot above is the honest, current list. We work through gaps as part of the regular build cycle. If you hit a specific barrier, report it below; user reports are one of the most useful signals we get.

We want to hear about accessibility barriers, or ideas for improvement. Email support@oltodiscovery.com. Include the page or feature, what you were trying to do, and the assistive technology and browser you were using. We’ll respond in a reasonable timeframe and work with you on a fix.