Sarabellum
Accessibility
Built to be usable — and honest about where it isn’t yet.
Sarabellum exists for people whose brains and bodies don’t match the default. Accessibility isn’t a compliance chore here; it’s the whole point. Here’s where we stand.
The standard we aim at
We aim to meet WCAG 2.1 Level AA across this website and the app. That means real semantic structure, keyboard operability, sufficient colour contrast, respect for reduced-motion preferences, and content that works with a screen reader.
What’s in place today
- Semantic HTML with proper landmarks (header, navigation, main, footer) and a “skip to content” link on every page.
- A visible keyboard-focus indicator, and a site you can navigate end-to-end without a mouse.
- Text-based menus and FAQs that work with JavaScript switched off.
- Colour contrast checked against AA in both light and dark themes.
prefers-reduced-motionis honoured — if your system asks for less motion, the animations stand down.- Form fields have real, associated labels, not placeholder-only hints.
- No third-party accessibility “overlay” widget — we consider those harmful, and we don’t use one.
Where it’s still rough
This is a one-person project in active development, so parts of the app are further along than others, and we haven’t yet had a formal third-party audit. If something gets in your way, that’s a bug we want to hear about — not an edge case we’ll wave off.
Found a barrier? Tell us.
Email aolsendev@gmail.com with what you were trying to do and what got in the way. It goes to a real person who will read it and fix what can be fixed. We treat access problems as priority bugs.
This statement is reviewed as the product changes. It describes our genuine current state, not an aspiration — if you find it out of date, that itself is worth reporting.