Accessibility
What has been built for accessibility, and how to tell us where it falls short.
These tools are built to be usable with a keyboard and a screen reader. Every input has a visible label, not a placeholder standing in for one. Focus order follows the reading order, focus is visible, and errors are announced and tied to the field they describe.
Implemented features
- Visible labels on all inputs and controls
- Keyboard operation for forms, segmented controls and diagram view switches
- Diagrams carry a title, description and an equivalent results table so they are not the only explanation
- Color is never the sole way concepts are distinguished; lines use distinct styles and labels
- Reduced-motion preferences are respected and animations are short
- Touch targets are at least 44 pixels and layouts reflow without horizontal scrolling
Known limits and feedback
Accessibility is an ongoing effort and this page does not claim a formal WCAG certification. If you hit a barrier, please report it through the contact page with the page and what went wrong, and it will be addressed.