Accessibility statement

Where we are

We want anyone who is learning to read music to be able to practise with SightReader, on the web and in our iOS and Android apps. We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA.

Today SightReader partially meets that standard: most of it does, and the parts that do not are listed below, with what we are doing about them.

What works

• You can play without a mouse or a MIDI keyboard: your computer keyboard plays the notes. Turn on key labels in your settings to see which key is which.
• Screen readers announce your result when a run finishes.
• The app follows your device’s reduced motion setting, and has its own Reduce animations setting as well.
• There is a dark theme, and text and pages scale with your browser’s zoom.
• Our grey secondary text meets the WCAG contrast ratio in both themes.

What does not work well yet

• The music itself is drawn as a picture. A screen reader can say that sheet music is there, but not read the notes, so practising a piece is not yet possible without sight. This is true of sight-reading apps generally, and we would like to do better.
• Some small text and button labels in our orange accent colour fall short of the contrast ratio. We are working through them.
• We have checked the main pages with automated tools but have not yet tested every flow with VoiceOver and TalkBack, so there may be problems we do not know about.

How we check

We run automated accessibility checks (axe) on the main pages at desktop and phone sizes, and the contrast of our text colours is checked every time the code changes. This statement was last reviewed on 20 October 2026.

Tell us about a problem

If something in SightReader is hard or impossible for you to use, please tell us at hello@sightreader.app or through our contact page. Say what you were trying to do and which device you use, and we will reply and fix what we can. If you need something in another format, ask and we will do our best.