v2.2.0

TickTune v2.2.0 — accessibility

An accessibility statement, and the barriers writing it found.

New

• ACCESSIBILITY.md: what is built in, what has been tested, what is known not
  to work, and how to report a barrier — the new "Accessibility barrier" issue
  form, or accessibility@poli0981.dev. The target is WCAG 2.2 AA; it is a
  target, not a claim.
• The single-key shortcuts (M, F, H, S, ]) can be switched off in Settings →
  Keyboard shortcuts — for speech input, or keys pressed by accident. Space,
  the arrows and Esc keep working.
• A screen reader can read the time remaining at any moment, in words. It is
  still announced only at 10, 5 and 1 minutes, 10 seconds and zero.
• The landing's looping demo has a "Stop the demo video" control.
• Windows Contrast themes: selected keys, tabs, switches and sliders now show
  their state in your theme's colours, and the landing's readouts no longer
  read "88:88".

Fixes

• Space on a focused button now presses that button. During a run it used to
  pause the music instead.
• Focus is no longer lost when the bottom bar fades or when time is up.
• The bottom bar's controls stay available to screen readers after it fades.
• A YouTube video that cannot play is announced once, not every second.
• The Setup source tabs move with the arrow keys; sliders say their unit; the
  reason "Match length" is unavailable reaches screen readers; the drop zone
  shows a focus ring; the drag handle is easier to hit.
• A desktop browser zoomed in when the page loads is told how to get in,
  instead of being told it is a phone.