Accessibility statement

The standard we follow

We aim to meet Israeli Standard IS 5568, which is based on the WCAG guidelines at level AA. Where WCAG 2.1 adds criteria beyond the legal floor, we have implemented them too.

What has been made accessible

• The page declares its language and text direction, and switches fully to right-to-left in Hebrew.
• A skip-to-content link is the first item reachable by keyboard on every page.
• The whole interface can be operated by keyboard, and the focused element always has a visible outline.
• Landmarks (banner, navigation, main, contentinfo) are marked up so screen readers can jump between regions.
• An accessibility menu on every page adjusts text size up to 150%, turns on a high-contrast palette, underlines links and reduces motion.
• The interface honours the operating system's reduced-motion setting without any configuration.
• Form fields have associated labels, required fields are announced, and validation errors are announced in the interface language.
• Colour contrast in both the standard and high-contrast palettes meets or exceeds the 4.5:1 ratio for body text.

Known limitations

We would rather state these plainly than claim conformance we have not verified:

• No independent accessibility audit has been carried out yet. The features above were implemented and checked internally.
• Performance mode is a full-screen playing surface built around touch and Bluetooth pedals. It is keyboard-operable but has had less screen-reader testing than the rest of the app, and the floating accessibility button is deliberately hidden there so it cannot block the page-turn area.
• Chord sheets are written by users. We cannot control the structure or wording of content another user has authored.
• Exported PDFs are not tagged for accessibility, so screen readers may not read them in a meaningful order.
• Screen-reader testing has been carried out informally rather than systematically across NVDA, JAWS and VoiceOver.

Contact us about accessibility

If you run into a barrier anywhere in this service, please tell us — describe the page and what happened, and we will look into it and reply.

• Email: [email protected]

Status of this statement

This statement was last reviewed on 2026-08-08. It is updated whenever an accessibility change is made to the service.