Accessibility

Last updated September 2026.

The short version. We want MyOrigins.io to work for people using a screen reader, a keyboard alone, browser zoom, or a different color and contrast setup than the default. We are actively working through gaps as we find them, and we would genuinely like to hear from you if something does not work well.

Our approach

MyOrigins.io is built around a conversational interview, which is itself an accessibility-minded design choice: talking or typing naturally is often easier than filling out long forms. Beyond that starting point, we aim to follow the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA where practical, including readable color contrast, keyboard operability, and clear page structure for screen readers.

What this looks like today

Known limitations

We are a small team and this is an evolving product. Some interactive elements may not yet have full keyboard or screen-reader support, and some pages have not had a complete accessibility audit. We are not aware of every gap - if you find one, please tell us.

Let us know

If you use assistive technology and run into something on MyOrigins.io that does not work the way it should, please email support and describe what you were trying to do and what happened. We read every message and will do our best to help and to fix the underlying issue.