Accessibility at Chronicle
Chronicle's web app was scanned with axe-core in a real browser on 10/29/2026, on all 16 captured views in light and dark. The first scan found real problems (low-contrast buttons and text, a missing level-one heading, unnamed chart bars, and a menu pattern the app did not honor); they were fixed the same day, and the rescan reported no violations. Keyboard, motion, and reflow checks were scripted too. Nobody has used it with a screen reader, and we do not claim a WCAG conformance level.

What Chronicle supports today
Each line says what the product does, how we know, and where to look. “Not yet tested” means exactly that: we have not checked, and we do not claim it.
Partly supported
Keyboard operation
The first Tab stop is a skip link that appears on screen, the sidebar is plain links in a labeled navigation landmark, and 24 Tab stops through the Alerts page each showed a visible focus indicator. Enter on a focused link opens its page. Other screens, and the arrow-key and Escape behavior of dialogs, have not been walked with a keyboard alone.
Evidence
- screenshots/captures/chronicle.spec.ts in the fleet harness, test 'a11y: keyboard path, focus rings, reduced motion, reflow, and phone width': the skip link is the first stop and on screen, 24 further Tab stops on Alerts all report an outline or shadow, and Enter on the Logs link navigates to /logs (recorded in a11y-evidence.json)
- the Chronicle repo's frontend/src/__tests__/a11yShowcaseFixes.test.tsx: the sidebar has no menubar or menuitem roles (it had a menubar with no arrow-key behavior until 10/29/2026) and sits in the Main navigation landmark
- Focus indicator contrast has not been measured, and only the Alerts page was tabbed through.
Partly supported
Screen reader landmarks and labels
axe-core found no violations on any captured view after the fixes: names, roles, labels, landmarks, one level-one heading, and named chart bars. The app has not been used with a screen reader, and live updates are not announced.
Evidence
- the harness spec runs axe-core 4.x (WCAG 2.0 to 2.2 A and AA plus best-practice rules) on all 16 views in both themes, 32 scans, and the rescan recorded zero violations (axe-all-states.json); the first scan found unnamed waterfall bars and, on the Overview page, a missing level-one heading
- the Chronicle repo's frontend/src/__tests__/overviewCounts.test.tsx: exactly one h1 once data loads; frontend/src/__tests__/a11y.test.tsx runs vitest-axe on the root route
Supported
Contrast in light and dark
Text, buttons, badges, and the active navigation item clear 4.5:1 in light and dark. The first scan found white text on the dark accent at 3.3:1, accent text on its tint at 4.0 to 4.4, and amber, red, emerald, and destructive text at 3.2 to 4.4; all were fixed with new accent tokens and darker shades.
Evidence
- axe-core color-contrast rule on all 16 views in both themes (32 scans) with zero violations after the fixes, from the harness spec (axe-all-states.json)
- the Chronicle repo's frontend/src/__tests__/a11yShowcaseFixes.test.tsx computes the contrast of the solid-button and accent-text tokens in both themes and fails if a page uses a color pair axe measured below 4.5:1
Supported
Reduced motion
With the reduced-motion setting on, animation and transition durations collapse to about a hundredth of a millisecond, through a rule in the design system's tokens that applies to every element.
Evidence
- the harness spec with reduced motion emulated: the navigation's transition duration and the body's animation duration both measure 1e-05 s (a11y-evidence.json)
- the Renkara design system's tokens.css, imported by the app's global.css: a prefers-reduced-motion rule on every element and pseudo-element
Partly supported
Text resize and zoom
The layout reflows without sideways scrolling at 640 and 320 pixels wide on all 14 routes in both themes, which is a 1280-pixel window at 200 and 400 percent zoom. Changing the browser's default font size has not been tested.
Evidence
- the harness spec: documentElement scrollWidth stays within the viewport at 640 and 320 pixels on /, /services, /logs, /traces, /alerts, /incidents, /issues, /slos, /dashboards, /deploys, /runbooks, /rum, /cost, and /search, in light and dark (a11y-evidence.json, 56 of the 84 recorded checks)
- A larger default font size in the browser settings has not been tried.
Partly supported
Mobile and touch
All 14 routes fit a 375-pixel phone screen with no sideways page scroll in both themes, and the sidebar becomes a slide-in menu opened by a labeled button. Some controls are under 44 pixels: the menu button is 36, the floating bug-report button 48 by 36, and the Acknowledge links on Alerts are 16 pixels tall.
Evidence
- the harness spec at 375 by 667: no horizontal scroll on the 14 routes in both themes, and the measured sizes of Alerts' controls (a11y-evidence.json, targetsAt375)
- the Chronicle repo's frontend/src/__tests__/Layout.test.tsx: the mobile menu button toggles aria-expanded
No WCAG conformance level is claimed for Chronicle. The checks are automated (axe-core and scripted keyboard, motion, and reflow passes) against a copy of the app running on fictional data; no one has audited it against WCAG or tested it with a screen reader or other assistive technology. The product's README states a WCAG 2.1 Level AA target, which is a goal.
What does not work yet
- Chronicle has not been tested with a screen reader, and live updates are not announced.
- Only the Alerts page was walked with the keyboard; dialogs have not been checked for Escape and focus return.
- Some controls are under 44 pixels on a phone: the menu button, the floating bug-report button, and the Acknowledge links.
- Focus indicator contrast has not been measured, and a larger browser default font size has not been tested.
How this site is built and checked
This site targets WCAG 2.2 level AA. That is a target we build and test toward, not a certification, and no one has audited it for conformance.
Structure
A skip link, labeled landmarks (header, navigation, main, footer), one h1 per page, and headings that do not skip levels.
Keyboard and focus
Links and buttons are native elements, so they work from the keyboard. Focus is drawn as a visible ring, and the menu closes with Escape.
Contrast
Text meets 4.5 to 1 in both the light and dark themes, checked against the stylesheet by the test suite.
Motion
Transitions and animation switch off when your system asks for reduced motion.
Small screens and zoom
Layouts hold at 375 pixels wide with no sideways scrolling, text resizes with the browser, and touch targets are at least 44 pixels.
Automated scan
Every page is scanned with axe-core at 375 and 1440 pixels in light and dark, and the checks fail on any serious or critical violation. Automated tools find only part of the problems, so this is a floor, not proof.
Images
Every product screenshot has a text description and comes in a light and a dark version that follows your theme.
Your theme choice
The theme follows your system setting until you pick one with the button in the header.
Statement last reviewed 10/29/2026.