Accessibility

Accessibility Statement

PianoMode is committed to making piano learning available to as wide an audience as possible — including learners using assistive technology. This page documents our current conformance, the areas we know still need work, and the contact channel for accessibility issues.

Last reviewed: May 12, 2026

Our standard

We target WCAG 2.2 Level AA across pages and interactive tools. Where a tool inherently relies on a sense (Ear Trainer requires hearing, Sight Reading requires sight), the surrounding navigation, lessons and account flows still meet AA so the rest of the site stays usable.

What works today

  • Keyboard navigation for the main menu, account flow, lesson accordion, quiz and learning-path templates.
  • Visible focus rings on every interactive element (buttons, links, form fields, the in-lesson mini-piano keys).
  • Semantic landmarks (<header>, <nav>, <main>, <footer>) so screen readers can skip directly to the lesson body.
  • Form fields paired with explicit <label> elements or aria-label; AJAX validation surfaces errors via role="status" live regions.
  • Honor prefers-reduced-motion for hover / scroll animations and the cookie-banner slide-up.
  • Honor prefers-color-scheme: full dark and light palettes via design-system tokens.
  • Color contrast on body text meets AA (4.5:1) on both palettes; UI controls meet AA (3:1).
  • Service Worker + PWA install support so the app works offline once a lesson has been viewed — useful on flaky mobile connections.

Known gaps we are working on

  • The OMR scanner currently lacks a non-visual review step: scanned sheet music is rendered with AlphaTab but not surfaced as a text transcript. We're scoping a "structure summary" output.
  • The Piano Hero falling-notes game is inherently visual; a keyboard-only practice mode is on our roadmap.
  • A few legacy CSS rules predate the design-system tokens. Dark/light parity for those rules is being audited round by round.
  • Captions / transcripts on every video lesson is in progress; auto-generated YouTube captions cover most lessons today.

Browsers and assistive tech we test against

  • Chrome 120+ on Windows / macOS / Android — with TalkBack and NVDA.
  • Firefox 120+ on Windows / macOS — with NVDA.
  • Safari 17+ on macOS / iOS — with VoiceOver.
  • Edge 120+ on Windows — with Narrator.

Reporting an issue

If something on this site is harder to use with assistive technology than you expect, we want to know. Please contact us with:

  • The page URL where the issue happened.
  • The assistive technology you used (screen reader name + version, keyboard, voice control, etc.).
  • What you tried to do and what happened instead.

We aim to acknowledge accessibility reports within five business days and ship a fix or a workaround within fifteen business days for blocking issues.

Statement scope

This statement applies to every page under pianomode.com, including the LMS templates, learning paths, score pages and the installable PWA. Third-party embeds (YouTube, Stripe checkout, Cloudflare CDN) are outside our direct control; we choose vendors with an active accessibility track record.

Formal compliance

PianoMode is a private project — there is no statutory disability non-discrimination obligation that applies to us today, but we follow WCAG 2.2 AA as a baseline and the related EN 301 549 guidance for European users.

Document version: 1.0 — May 12, 2026

Need help with a specific feature or workflow?

Visit the help center