Accessibility
Every product page on the internet claims to be accessible. This page says what was actually tested, on what, and what is still unverified — including the things that are not finished.
This website
- Semantic HTML with a single main heading per page and no skipped heading levels.
- A skip link to main content as the first focusable element.
- No images of text. Nothing conveyed by colour alone.
- Light and dark themes that follow your system setting.
- Full keyboard operation. Visible focus everywhere.
- No JavaScript. Nothing on this site requires it, so there is none to fail.
The applications
Each app ships its own accessibility statement covering what was tested and what was not. The short version of the approach:
Native controls only. Every slider, combo box and checkbox is a real operating system control. Custom-drawn widgets photograph better and tell a screen reader nothing. Artwork goes on the splash screen, the About box and this website — never between you and a control.
Value announcements, not just names. A slider that announces "Gain, slider" without the number is not usable. The number is the entire point.
Key travel is a real accessibility property. A control you can technically reach but which needs hundreds of key presses to adjust is not accessible in any sense that matters. Every slider in TG Model Master is between 28 and 200 presses end to end, and that was a bug fix, not a design that happened by accident.
Speech that can be interrupted and silenced selectively. Different kinds of message go on different channels so that muting one does not mute the others.
Written for text to speech. Units are spelled the way a screen reader should say them — "d B", "B P M", "I R file" — rather than as abbreviations that get mangled.
What is not verified yet
Being straight about this, because a claim you have not checked is just a claim.
- TG Model Master has not yet been through a full NVDA pass on real hardware. It is built to the rules above and tested headlessly, but no screen reader has been on it end to end. Specifically unverified: whether arrowing a slider announces once or twice, and whether NVDA reads the raw underlying integer instead of the formatted value.
- JAWS and Narrator are untested. The design should work with both. Should is not the same as does.
- Mac and mobile do not exist yet. Windows only for now.
That list will shrink. It will not be quietly deleted — when something is verified, this page will say what was tested and on which version.
Standards
The website targets WCAG 2.2 Level AA. A VPAT for the applications is planned before they go on sale, because the institutions most likely to buy this — schools for the blind, rehabilitation agencies, assistive technology vendors — ask for one as a matter of course.
Found something broken?
That is genuinely useful and I would rather hear it than not. Tell me what you were using, which screen reader and version, and what happened.