Accessibility

Last updated: 2026-09-28

We want craterio.com to be usable by as many people as possible, including people using screen readers, keyboard-only navigation, or who need higher-contrast text. We're targeting WCAG 2.1 Level AA as our standard, and this page tracks where we actually stand against it.

What's in place

Text and background colors checked against WCAG AA contrast ratios (4.5:1 for normal text, 3:1 for large text) and corrected where they fell short
A "skip to main content" link for keyboard users, so you're not forced to tab through the full navigation on every page load
The sign-in and feedback dialogs are marked up as real dialogs (role="dialog", labelled headings) so screen readers announce them correctly
Form fields have explicit labels, not just placeholder text, which screen readers don't reliably announce
Semantic HTML headings and a single top-level heading per page

Known gaps

We haven't yet done a full keyboard focus-trap inside the open dialogs (focus can currently move behind the dialog while it's open), and we haven't run a complete audit against every WCAG 2.1 AA success criterion — this is an ongoing pass, not a one-time certification.

The desktop app

This page covers the website. The Craterio plugin and standalone app is a custom audio interface and doesn't yet follow macOS accessibility APIs (VoiceOver, etc.) — that's a larger undertaking we haven't started.

Found an accessibility problem, or something that doesn't work with the tools you use? Tell us via the feedback form on the Craterio homepage — we read every submission.