Skip to content
XtremeLabs
Login to Helix LabsBuy

Accessibility

Accessibility is product behavior.

This product is built as software, so accessibility is part of how it behaves rather than a pass made over it at the end. What has been implemented is below, and so are the known limits.

What is implemented

  • Semantic structure on every route: one first-level heading, ordered heading levels, and landmark regions with names.
  • A skip link to the main content, and a main region that can receive focus.
  • Full keyboard operation of every interaction, including the architecture map, the simulated console, the sequencing exercise, and the lab session. Custom widgets follow the expected pattern for their role, with arrow-key movement where the pattern calls for it.
  • Visible focus everywhere, with a light ring on dark surfaces and a dark ring on light surfaces. Focus is never removed.
  • State changes announced through polite live regions rather than through color or position alone.
  • Text contrast of at least 4.5 to 1 for body sizes. The lighter brand blue is used for large text and for graphics on dark surfaces, never for body text on white.
  • Touch targets of at least 44 pixels on controls, at every breakpoint.
  • Reduced motion respected. Where a sequence is animated, the end state is rendered immediately instead, and no information exists only in the movement.
  • An equivalent structured mode for every interactive visualisation: the Helix architecture map has a full table, the console annotations have a definition list, the hotspot diagram has a described relationship list, and every chart carries either a data table or a complete text description.

Known limits in this prototype

  • The charts in the Ideas analysis article keep a minimum plotting width and scroll horizontally on a small screen rather than redrawing, because shrinking them would set the axis labels below a legible size. The data table below each chart carries every value.
  • This prototype has not been through an assistive technology audit with users. Behavior has been implemented against the patterns and verified by keyboard, not validated by the people who depend on it.

Reporting a barrier

A barrier in a learning product is a barrier to the qualification behind it, so it is treated as a defect and not as feedback.