Accessibility

Built for gross-motor-only input

Touchtone has no precision target anywhere on its play surface. Every touch that lands anywhere near a shape counts as touching it — there's no small button to miss, no fine drag to get exactly right, no double-tap timing to learn. If you can reach the screen with a finger, a knuckle, or a palm, you can play it.

Two people can share one iPad at the same time. The surface reads touches from anywhere on it at once, not one point of control that has to be handed back and forth.

Nothing you do is wrong

Touchtone has no error states. None. When you ask for something it can't give you — a system that's already full, say — it doesn't show a dialog, an alert, or a red X. It refuses physically: everything on screen pulses together for a beat and a low thud plays, and then you're free to try something else. Nothing is ever explained, because nothing ever needs to be.

Nothing to read

There is no text anywhere on the play surface — not a label, not a caption, not a tooltip. Everything you can do, you do by touching, holding, or dragging a circle directly.

Every line, ring, and arm on screen is drawn at a constant 4 points wide, at every zoom level. Pulled all the way back to see everything you've built, or in close on a single note, the outline never thins into a hairline you can lose.

Nothing hidden in a menu

Touchtone's own design law forbids menus, tabs, bars, and tracks on the play surface — there's no settings screen to navigate into, no icon that opens a hierarchy. Circles, held or dragged, are the entire vocabulary. The few things that don't fit on the surface itself reuse a single existing gesture — a hold — rather than adding a new one to learn for each.

This website, specifically

Everything above describes the Touchtone app. This site is being built to the same baseline every Manolab site starts from — semantic HTML, real headings and landmarks, keyboard-reachable controls with a visible focus ring — but as of this writing that baseline hasn't been checked against WCAG with tooling, because the pages it applies to are still being built.

We're not naming a conformance level here, because no one has measured one yet, and doing that would be exactly the kind of unverified claim this page exists to avoid. A measured pass — contrast checked arithmetically, a keyboard-only walkthrough, the pages read with styles and scripts off — runs before this site is considered finished, and this section gets rewritten with real numbers once it has.

Feedback

If anything on the app or this site gets in your way — something you can't reach, can't read, or can't operate — tell us. Describe what you were doing and what happened; we treat accessibility reports as bugs, not requests.

• Get in touch

About this statement

This statement was last reviewed on 25 September 2026. It describes the shipped app in full; the website section above will be updated once its own verification pass has run. We review this page whenever the app or the site changes in a way that could affect accessibility.