Accessibility statement

Accessibility

Last updated: June 12, 2026

I want Kaldrik to be usable by as many people as possible, including people who rely on keyboards, screen readers, or other assistive technology. This page explains what I'm doing to get there, where Kaldrik may still fall short, and how to tell me about an accessibility problem so I can fix it.

Kaldrik aims to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. I treat that as the target I'm working toward, not a box I've checked. Some parts of the app meet it today, others don't yet, and I'm improving them over time.

An honest note

Kaldrik is a beta product built by one person, in my own time. I care a lot about getting this right, but I don't have a dedicated accessibility team or formal audits, so some areas will be more polished than others and I'll inevitably miss things. I'd genuinely rather hear about a problem than have you work around it, so please reach out (details below) and I'll address it on a best-effort basis.

What's in place today

Where Kaldrik may fall short

Because Kaldrik is in active development, some areas are not there yet. Complex, highly visual tools (such as the arrangement grid, drag-and-drop stage plot, and tempo map) can be harder to operate without a pointer, and I'm still improving their keyboard and screen-reader support. Newer features may also lag behind on accessibility until I catch up. If you hit a wall, tell me and I'll prioritize it.

Reporting an accessibility problem

If something is hard or impossible to use, please reach me through the contact page. It helps if you can include the page or feature, what you were trying to do, the assistive technology or browser you're using, and what happened. I read every message and will work to address issues on a best-effort basis. If you need information from Kaldrik in a different format in the meantime, let me know and I'll do my best to help.

Contact

Questions, feedback, or an accessibility issue? Use the contact page.