Skip to main content

Accessibility  ·  Statement

Accessibility is the design, not the disclaimer.

I built Rhythmos for neurodivergent brains from the first commit. Accessibility was never a layer bolted on at the end to satisfy a checklist. It’s just how the app is made, and this site inherits it. Below are the choices I made on purpose, and the gaps I haven’t closed yet.

01  —  The choices

Choices I made on purpose.

  • No red, anywhere.

    Being behind isn’t an emergency. The app uses no warning red. The website inherits the rule. Errors, by rule, are body text on a soft surface. Never a red banner.

  • A font built for reading.

    The whole site is set in Lexend, a typeface designed specifically to make reading easier, with its extra legibility features switched on. It’s the only font here, on purpose. Headings stand out through size and weight, not a second decorative face.

  • Motion, but only when you want it.

    Animations honor your device’s reduced-motion setting. If you’ve asked your system to reduce motion, every transition on this site drops to zero. Not a polite reduction, a hard cut. The fade-in on the headline above didn’t run for you if you have it on.

  • Visible focus, everywhere.

    Tab to any button or link and it gets a clear outline in the brand blue. Nothing here strips the focus outline or hides it, so you can always see what you’re about to click.

  • Skip to content.

    The first focusable element on every page is a Skip to main content link. Open any page fresh, press Tab once, hit Enter, and you’ve jumped past the header.

  • Plain language, no diagnoses.

    No “disorder,” “deficit,” “meltdown,” or “comorbidity” appears anywhere in the app or on the site. The product is for neurodivergent brains; it does not speak about them in clinical terms.

  • Generous reading rhythm.

    Body text gets roomy line spacing, and reading-heavy pages keep their lines short enough to scan comfortably. Tired eyes shouldn’t have to fight the layout to find the next line.

  • Honest semantic structure.

    Headings are real headings and lists are real lists underneath the styling. Screen-reader users get the same structural map you see on the page, read in the order it’s meant to be read.

02  —  Right now

What this page is doing as you read it.

Receipts. Verifiable claims about this very page, not the site in general.

  • The text you’re reading is dark grey on white. The contrast measures around 10:1, comfortably past WCAG AAA, the strictest standard.

  • The Skip to main content link is the first focusable element on this page. Open it fresh, press Tab, and you’ve already skipped the header.

  • If your OS has reduced-motion enabled, the headline above didn’t fade in. It just appeared.

  • The waitlist text links on this site are underlined, and the Join waitlist buttons are solid pills. Neither relies on color alone.

  • Errors on this site, by rule, are never red. The strongest signal you’ll get is a line of dark grey text under the form.

03  —  Honest gaps

Where I haven’t shipped yet.

Rhythmos is pre-launch. There’s plenty I haven’t done. I’m putting it here so it’s part of the record, not buried in a backlog.

  • No screen-reader testing yet. TalkBack is first on the list.

  • No high-contrast or dark theme on the website. In the app, dark mode follows your phone, and there’s no high-contrast mode yet.

  • No user testing with diverse assistive-tech users yet. That’s a launch-side activity, not pre-launch.

  • English only. Translation is a post-launch project.

  • The Rhythmos app itself is Android-only at the moment.

04  —  If something doesn’t work for you

Tell me. Plainly.

The cleanest path is email. Write to support@getrhythmos.com and I read it directly. A public Rhythmos issue tracker on GitHub is in the works; once it’s open I’ll add a link here.

I don’t promise instant fixes. I do promise honest replies, no defensive language, and a public record of what I did or didn’t change in response.