Last updated draft - not yet reviewed
We want time-tracker to work for everyone, including people using a keyboard, a screen reader, or other assistive technology. This page describes our target and where we currently fall short of it.
We aim to meet WCAG 2.2 Level AA. Every screen is built to be fully keyboard-operable, and we test with automated checks (axe) on every page and component state, plus periodic manual passes with a screen reader.
The Day view's visual calendar is a pointer-and-keyboard enhancement over the block data - it is not, itself, a screen-reader-navigable data structure. Everything the calendar can do (create, move, resize, and delete a time block) is also fully available through the list view, which is the accessible-equivalent path for every action. If you use a screen reader, the list view is the one we'd recommend.
On narrow screens, the export table becomes a list of day cards instead of a grid. This layout is functional and passes our accessibility checks, but has had less visual polish than the desktop table.
If you hit an accessibility barrier using time-tracker, we want to know. Contact [accessibility contact email to be added before launch] and tell us the page, what you were trying to do, and what assistive technology you were using - we'll get back to you and aim to fix genuine barriers.