Accessibility in a SOC tool is not a legal formality. It is operational safety. The analyst three hours into a night shift is not reading your interface — they are pattern-matching it, under fatigue, looking for the one thing that breaks the pattern.
Contrast is triage
If the secondary metadata fails contrast, it is not "slightly harder to read" — it is gone, exactly when it matters. We verify contrast at the token layer so an inaccessible combination cannot be expressed in the first place.
ts
// Contrast verified at the token boundary, in CI.
expect(contrast(tokens.fgMuted, tokens.cardBg)).toBeGreaterThan(4.5);
// A failing token fails the build — not the audit.You do not pass an accessibility audit by remediation. You pass it by making the inaccessible state impossible to express.
Beyond color
- Status is never color-only; every state carries a label or glyph so meaning survives colorblindness and low brightness.
- Focus order follows the triage flow, not the DOM accident — keyboard-only analysts move the way the work moves.
- Motion is restrained; nothing animates that would distract from the one row that just went critical.
Designed this way, accessibility stops being a checklist and becomes the thing that lets a tired human do dangerous work correctly.
