How Oria should stay usable for everyone.

Oria should be usable by people who navigate with screen readers, keyboards, switch devices, voice control, zoom, captions, and other assistive technologies.

Our target is WCAG 2.2 AA across the intake, results flow, saved-results recall, and branded emails.

The current product direction includes labeled fields, visible validation feedback, keyboard-focusable controls, meaningful image alt text, and layouts that should remain readable on mobile without relying on pinch-zoom.

For blind, low-vision, deaf, hard-of-hearing, and mobility-impaired users, best practice also includes testing with screen readers, keyboard-only navigation, contrast review, touch-target checks, and accessible transactional emails.

Publishing an accessibility statement does not itself make the product compliant. Accessibility requires continuous engineering, QA, and content review as the funnel changes.

If Oria is embedded on another website, the embedded version should still preserve accessible labels, notices, links, and keyboard behavior instead of relying on the host page alone.

If you need help using Oria or want to report an accessibility barrier, please contact us through the email listed in your results or on this page.