Accessibility · Security · Data processing

Accessibility

Last reviewed 3 June 2026

We want everyone to be able to learn how the music industry’s money really works, regardless of how they read, hear, or operate a screen. This statement describes what we’ve built, where we know we fall short, and how to tell us when something doesn’t work for you.

Our commitment

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. Accessibility isn’t a one-off audit for us. It’s a build constraint we test on every change, and we treat a regression as a bug.

What we’ve done

AA-contrast-guarded colour.Our text and surface colours are defined as design tokens, and an automated test reads those real tokens and fails the build if any content-text/background pair drops below the WCAG AA contrast ratio (4.5:1). Contrast isn’t left to chance. It’s enforced.
Keyboard-operable interactive lessons.The interactive “beats” (predict-the-answer, drag-to-order, match, allocate, and the live simulators) are operable by keyboard, with visible focus outlines and labelled controls. Sliders expose an accessible label and a spoken current-value text.
Screen-reader alternatives for charts. Visual data (charts, waterfalls, distributions) is paired with an equivalent data-table or text alternative, so the numbers are available to assistive technology, not just to sighted users.
Reduced-motion support. We respect the operating-system prefers-reduced-motion setting and tone down or remove non-essential animation for people who ask for less movement.
Semantic, no-PII public path. The free lessons need no sign-in and use semantic headings and landmarks, so a screen reader can navigate the structure.

Known limitations

We’re honest about where we’re not done yet:

A small number of complex interactive visualisations (for example, the follow-the-money graph explorer) are richer visually than via assistive technology; we provide the underlying data elsewhere but the explorer itself is not yet fully non-visual.
We have not yet completed a formal third-party audit or published a VPAT; our conformance claim is based on our own automated and manual testing.
Some illustrative figures are labelled visually as “Illustrative”; we are working to make sure that label is consistently announced to screen readers.

How to report a problem

If you hit an accessibility barrier, anything you can’t read, reach, or operate, please tell us. Use our contact form (pick the Accessibility topic) and include the page, what you were trying to do, and the assistive technology or settings you use if you can. We treat these reports as bugs and will respond promptly.