Accessibility at Daybook
Daybook’s web app has native controls, labeled editor fields, and a layout that changes to one column on a narrow screen. The product evidence below is limited to source inspection and a scripted seven-view scan; no WCAG conformance level is claimed.
What Daybook 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 web app uses native links, buttons, and labeled fields. A scripted Tab check reaches a control on Timeline. A complete keyboard audit has not been performed.
Evidence
- frontend/src/components/Sidebar.tsx and frontend/src/pages/EditorPage.tsx: native controls and field labels
- captures/daybook.spec.ts: first Tab stop on Timeline
Not yet tested
Screen reader landmarks and labels
The web app has not been tested with a screen reader. Automated checks do not establish how the journal reads aloud.
Supported
Contrast in light and dark
The automated color-contrast rule found no violations on the seven scanned views at 375 and 1440 pixels, in light and dark. This is not a complete manual audit.
Evidence
- captures/daybook.spec.ts: axe-core color-contrast, seven views, two widths, both themes, 11/04/2026
Not yet tested
Reduced motion
The capture uses the reduced-motion preference. A preference-by-preference motion audit has not been performed.
Not yet tested
Text resize and zoom
Text at 200 percent has not been tested in the product.
Partly supported
Mobile and touch
The web layout changes to a single column below 760 pixels. The recorded scan checks seven views for sideways page scrolling at 375 pixels.
Evidence
- frontend/src/styles.css: single-column layout and editor below 760 pixels
- captures/daybook.spec.ts: page overflow at 375 pixels, in both themes
Daybook has not received a full accessibility audit or assistive-technology test. The showcase itself is checked with axe-core at phone and desktop widths in both themes.
What does not work yet
- No screen-reader, complete keyboard, or 200 percent text-resize audit has been performed.
- The automated product scan records any remaining findings by rule and view.
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 11/04/2026.