Last reviewed: April 2026Scope: shellr, DMA, docsFocus: keyboard, focus, mobile tables
Why this matters
Public platform surfaces should remain usable under keyboard navigation, reduced motion, zoom, and mobile constraints. That is part of platform quality, not a separate design phase.
Current Baseline
What is already in place.
Skip links on the public-facing pages and docs site.
Visible focus indicators across navigation, buttons, and inputs.
Reduced-motion-safe reveal handling on the landing page.
Server-rendered status snapshot so the public status entry does not depend fully on JavaScript.
Scrollable DMA table containers to avoid clipped mobile layouts.
Known Limits
What still needs review whenever the UI changes.
DMA remains data-heavy, so dense tables still need manual mobile review after UI changes.
Uptime Kuma itself is still a JavaScript-heavy app behind the public snapshot layer.
Any new landing-page motion should continue to degrade cleanly under reduced motion and missing observer support.