Accessibility
Our commitment to making openworld.dev usable by everyone, and how to tell us when it falls short.
Effective September 8, 2026.
Our commitment
OpenWorld wants everyone who visits openworld.dev to be able to read it, move through it, and get in touch with us, whatever technology they use to browse. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA and to keep the Site at that level as it changes.
What we do
Accessibility is built into how the Site is made rather than added afterwards. The Site:
- Uses semantic HTML, with one heading outline per page, named landmarks, and a skip link to the main content.
- Works with a keyboard alone, with visible focus on every interactive element.
- Keeps text and interface colours at or above the contrast ratios WCAG requires, and never relies on colour alone to convey meaning.
- Gives images meaningful alternative text, and hides purely decorative graphics from assistive technology.
- Respects the reduced-motion preference in your operating system, turning off animation and marquee movement.
- Scales cleanly with browser zoom and larger default text sizes, and works on small screens.
- Makes touch targets large enough to use comfortably.
We test the Site with automated tools, including Lighthouse and axe, and by hand with a keyboard and screen readers, and we re-test when pages change.
Known limitations
Some content is outside our direct control. Our regulatory filings are hosted by the U.S. Securities and Exchange Commission on EDGAR, and their accessibility depends on that service and on the format in which filings are prepared. Contact forms open your own email application, whose accessibility is governed by that application.
The home page includes a rendered three-dimensional scene. It is decorative, hidden from assistive technology, and the page reads fully without it.
Tell us about a problem
If any part of the Site is difficult to use, or you need information in a different format, email connect@openworld.dev and tell us the page, what happened, and the browser or assistive technology you were using. We will reply, and we will fix what we can.