TG StudiosAccessibility
What was actually tested, on what, and what is not verified yet.
This website
- Semantic HTML, one main heading per page, 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, so there is none to fail.
The applications
Each app ships its own statement. The approach:
Native controls only. Every slider, combo box and checkbox is a real operating system control. Custom-drawn widgets tell a screen reader nothing.
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 counts. A control you can reach but which takes hundreds of presses to adjust is not usable. Every slider in TG Model Master crosses in 28 to 200 presses.
Speech that can be silenced selectively. Different kinds of message go on different channels, so 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".
What is not verified yet
- TG Model Master has had no full NVDA pass on real hardware. Built to the rules above and tested headlessly, but no screen reader has been on it end to end.
- JAWS and Narrator are untested. The design should work with both. Should is not does.
- No mobile. Desktop only, TG Spaces on Windows and macOS, TG Model Master on Windows.
This list will shrink, not quietly disappear.
Standards
The website targets WCAG 2.2 Level AA. A VPAT for the applications is planned before they go on sale, the institutions most likely to buy ask for one.
Found something broken?
Tell me what you were using, which screen reader and version, and what happened.