Accessibility

What the site does

• Every page works with a keyboard alone, and the focus outline is visible and never removed.
• A skip link jumps past the masthead to the answer.
• Every page has one first-level heading, and the headings below it descend in order.
• The tables are real tables with real column headers, not grids of styled text.
• Every slider, field and select has a label that is attached to it rather than sitting near it.
• The dial is decorative and carries a text description; every number it shows is in the table beside it.
• The moon and the sun at the top of each page are decoration and hidden from screen readers. Text is laid out around them and never on top of them, so they cannot cost any text its contrast.
• Nothing moves except short transitions and the moon or the sun rising a little into place as the page loads, once. When your system asks for reduced motion, both are switched off.
• Both the dark and light schemes are checked for contrast, and the light scheme exists partly because a dark page does not suit everybody.
• Nothing blocks pinch-zoom, and no page scrolls sideways on a phone 320 pixels wide. A table with more columns than that scrolls inside its own box, which can be reached and scrolled with the keyboard.
• Every table on the site is correct with JavaScript switched off, at the stated default assumptions. Anything you change needs it: the sliders and time fields, the 12h and 24h and theme switches, the travel planner, the week's tally, a rota, the calendar files, the find-your-cycle notebook, the settings link and the offline copy.

Where it is weaker

The sliders are the hardest part of this site to use without a pointer. They are ordinary range inputs, so arrow keys move them, but a reader who wants an exact cycle length has no way to type one. That is a known shortcoming rather than an oversight, and the tables are correct at the default values without touching a slider at all.

Telling us

If a page is unusable for you, write to hello@duskdial.com and say what you were trying to do and what got in the way. It is treated as a bug, not as a feature request.