Talento
Sign in

Legal

Accessibility

What has been done to make Talento usable for everyone, what has been measured, and what has not yet been tested.

Last updated 8 September 2026

Where we stand

Talento aims at WCAG 2.2 Level AA. It is partially conformant: parts of it have been measured against that standard and meet it, and parts have not been tested at all. The honest state of each is below.

What has been measured

Colour contrast. Every text colour in both the light and dark themes was fitted numerically against the surface it actually renders on. Because panels here are translucent, each colour was checked against the composite a reader really sees, not against the panel’s nominal colour — fitting to the latter passes on paper and fails on screen. The worst measured pair is 4.61:1 in light and 4.83:1 in dark, against an AA floor of 4.5:1.

Colour is never the only signal. Pipeline states carry a text label beside the coloured dot, so the six stages remain distinguishable without colour vision.

Keyboard focus. Focus is visible everywhere, as a two-pixel outline in the accent colour with an offset so it does not sit on the control’s own edge. The browser default is never removed without a replacement.

Motion. The only thing that moves on its own is the loading ring beside work in progress. If your system asks for reduced motion it is shown as a still ring, and hover transitions are cut to effectively zero.

Text scaling and reflow. Layouts use relative units and wrap. Wide content — tables, long URLs — scrolls inside its own container, so the page itself never scrolls sideways.

What has not been tested

Screen readers. The product has not been tested with NVDA, JAWS or VoiceOver. Headings, landmarks, form labels and the current-page state are marked up properly, but marked up correctly and verified as usable are different claims and only the first one is true today.

Voice control and switch access. Untested.

Full keyboard traversal. Individual controls are reachable and focus is visible, but no complete pass has been done to confirm every task can be finished without a mouse.

Known problems

The console’s dense tables render at 13px so an operator can compare many rows at once. That is below a comfortable reading size, and browser zoom is currently the only answer.

The navigation scrolls horizontally on a narrow window rather than wrapping. It stays reachable by keyboard, but the scroll affordance is easy to miss.

Telling us about a problem

If something here blocks you, please say so — a specific report about a specific page is worth more than any audit. Write to [ACCESSIBILITY CONTACT — email address] and describe what you were trying to do, what happened, and what you were using.

We aim to reply within [RESPONSE TARGET — e.g. 5 working days]. If a reply does not come, or does not resolve it, you can escalate to [ENFORCEMENT BODY — jurisdiction dependent].