Accessibility Statement
Last updated: 3 September 2026
We want Annotune to be usable by as many people as possible and we work towards the WCAG 2.2 Level AA success criteria.
What we currently do
Interactive controls have accessible names, including icon-only buttons for zoom, paging, export and navigation. Forms use visible labels and report errors in text rather than through colour alone. Dialogs and sheets manage focus and close with Escape. Page zoom is not blocked, and the interface reflows down to a 375 pixel viewport width.
Known limitations
Rendered sheet music is produced by the notation engine as SVG, which assistive technology cannot read as music. Every score therefore also has a text view (the Text tab in the editor, and “Score as text” below shared, demo and catalogue scores) that lists each measure’s key, time signature, tempo, dynamics, repeats, and every staff’s notes and rests by beat, with previous/next navigation; the underlying MusicXML also remains downloadable. The text view does not yet describe articulations, slurs, lyrics or ornaments. Payment fields are rendered inside a Stripe component we do not control. Internal administration screens are not translated and receive less accessibility testing than customer-facing pages.
Deliberate design choices
The score canvas keeps a white background in dark mode so that printed and exported output matches what is shown on screen.
Feedback
If you encounter a barrier, please contact us using the details in the legal notice (Impressum) or through the contact form. Tell us the page and what you were trying to do, and we will respond and describe how we intend to address it.