Accessibility statement
Accessibility is an engineering requirement and an ongoing verification task, not a certification claim.
Implemented support
The workspace uses semantic controls, visible focus, labelled tables and mobile records, 44-pixel primary targets, dark mode, reduced motion, forced colors, and 320-pixel reflow. The cue queue is a single-tab-stop listbox: Tab reaches it once, then arrow keys, Home, End, Page Up, and Page Down move the current cue.
Known boundaries
Dense project records can require substantial reading. Generated reports depend on browser print behavior. Automated scans cannot establish assistive-technology usability or conformance.
Further device testing
Complete real-device keyboard and screen-reader sessions, high-contrast checks, large-text review, and the support contact on this site. Record verified limitations rather than claiming certification.
Worked example
The cue queue holds one hundred cues in the sample, which is exactly the case where a naive list becomes a keyboard trap of a hundred tab stops. It is implemented as a single-tab-stop listbox instead: Tab reaches the queue once, then the arrow keys, Home, End, Page Up and Page Down move the current cue, and Tab moves on to the next control.
At three hundred and twenty CSS pixels the station layout reflows to a single column rather than scrolling sideways, primary targets stay at forty-four pixels, and each mobile record keeps its own label rather than relying on a column header that has scrolled out of view.
Method
The workspace uses semantic controls, visible focus, labelled tables and labelled mobile records, forty-four pixel primary targets, dark mode, reduced-motion handling, forced-colors support and reflow down to three hundred and twenty pixels. Automated accessibility scans run in the browser test suite against the public pages and every populated station.
Automated scans catch a defined subset of problems. They cannot establish that a person using a screen reader can actually complete a session.
What this does not do
- No conformance or certification claim is made.
- Dense project records still require substantial reading, and generated reports depend on browser print behavior.
- Real-device keyboard, screen-reader, high-contrast and large-text sessions remain testing still to be completed.
Do this in the app
Test the hardest station first, which is the hundred-cue queue.
- Open station 02 Cues and move through the queue using only arrow keys.
- Zoom to two hundred percent and confirm the layout reflows rather than scrolling sideways.
- Report barriers through the support contact on this site.
Open the local workspace at station 02 Cues