Accessibility pass on the registry and detail pages

[dubemoyibe-star]

Context

The dashboard was built dark-mode-only with a focus on visual design, and hasn't had an accessibility review. Since the core output is a number whose meaning depends on context — 54 means nothing without knowing the scale and direction — screen reader and keyboard users are poorly served by a score rendered as a bare styled number.

Scope

In scope: semantic markup, keyboard navigation, focus states, contrast verification against the dark palette, and meaningful labels on the score display and factor breakdown.
Out of scope: light mode, and any visual redesign.

Acceptance criteria

• Score displays carry accessible labels conveying scale and direction, not just the raw number
• Factor breakdown is navigable and comprehensible without seeing the visual layout
• All interactive elements reachable and operable by keyboard, with visible focus states
• Contrast ratios verified against WCAG AA across the dark palette; failures fixed rather than noted
• Registry rankings convey their ordering semantically, not only through visual position
• Verified with an actual screen reader, not only an automated audit tool

Difficulty

Intermediate — needs familiarity with the codebase or methodology

Notes / open questions

Automated tools catch maybe half of this. The score-in-context problem in particular won't show up in an automated pass but is the most consequential thing here.

[waterWang]

I'd like to work on this accessibility pass. My plan:

1. Semantic markup: Convert the registry grid to proper table semantics (role="table" / role="row" / role="cell" or <table> with role="presentation" on wrapper divs)
2. Score labels: Add aria-label to score displays conveying scale and direction (e.g. "74 out of 100, higher is safer")
3. Factor breakdown: Add aria-label and role="region" to factor cards for screen reader navigation
4. Focus states: Verify all interactive elements have visible focus indicators; add focus-visible: ring styles where missing
5. Contrast: Verify WCAG AA compliance for text on dark background; fix any failures
6. Registry rankings: Add aria-sort and semantic ordering cues
7. ScoreRing SVG: Add role="img" with descriptive aria-label; mark decorative elements as aria-hidden
8. Status indicators: Add aria-label or aria-live to the status pill's animated ping dot

I'll submit a PR when done.