Accessibility
My Speech Log is built to be usable with a keyboard, with a screen reader, at large text sizes and on an old phone. This page says what it holds itself to, names the one screen that deliberately does not meet it, and — at greater length — says what has not been checked.
Last reviewed by hand on 16 August 2026.
What it aims at
WCAG 2.2, Level AA, with one exception named below. That is a target the app has assessed itself against. Nobody independent has evaluated it, and this page is not a formal conformance statement.
Some of it is above the level rather than at it. Everything you tap is at least 44 pixels across, where AA asks for 24. Every state that is shown in colour is also written in words — a Level is met or short of one elective, never only green or only amber.
One screen does not meet it: the timing lights
While a speech is being timed, the speech timer fills the screen with a single flat colour — green, then amber, then red. There is no word on it and no row of lamps to read a position from, so the meaning is carried by colour and by nothing else. That fails 1.4.1 Use of Color, and this page says so rather than arguing it away.
The reason it stays that way: the screen is a replacement for a box of coloured cards held up at the back of a room, and a second signal on it would be a second signal no club has ever used, added to the one screen in the app that is read by someone who is currently speaking. The elapsed clock is on screen throughout, but it is there for the Timer to report from — the speaker cannot read it at that distance and does not know the thresholds it is being judged against, so counting it would be this app telling itself a story.
The exception is the running screen, and nothing wider than it. Before the clock starts, the screen carries words — what to tap, and what the timings are set to. The timer’s setup, its controls and its clock are all fully in scope and are ordinary labelled buttons.
If you are timing a speech and cannot use the colours, the timings you set are shown in words on the screen before you start.
What has actually been checked
Three things, and only the first happens automatically.
An automated check on every change
A linter with roughly thirty accessibility rules runs before any change can be merged, and it passes across every screen. It catches missing image descriptions and misused labels. It cannot see anything about how a page actually behaves.
A manual pass on every screen that changes
Four checks, by hand: that every action can be reached by keyboard and shows where the focus is; that nothing pinned to the screen covers the thing you have just focused; that the page still works in a window 320 pixels wide; and one pass with a screen reader over the screen being changed.
Colour contrast, measured
The text colours were measured against the surfaces behind them rather than assumed. Three combinations failed and were changed, and the measurements are recorded alongside the colours themselves.
What has not been checked
This is the longer list, and it is here because a page claiming a clean bill of health would be worth less than no page at all.
No page has ever been scanned by a tool
The automated check above reads the code, not the finished page. A scan of real, rendered screens has not been run. It is planned, and it arrives with the first browser-driven testing this app has.
There has been no audit of the whole app
The manual pass runs on the screen being changed. A screen nobody has touched for a while has not been re-checked since the day it shipped, and no sweep of every screen at once has been done. Closing this means one deliberate pass over all of them, which has not been scheduled.
Nobody who relies on assistive technology has tested it
The screen-reader passes are run by the person building the app, who does not use one daily. That finds obvious breakage and misses the rest. This is the gap the email address below exists to close, and it is the one that most needs you.
Two controls ignore “reduce motion”
The on/off switches and the dot in a radio button animate with a slight bounce even when your device asks for reduced motion. The moving parts elsewhere — the quotes that drift across the front page, the waiting indicator — do honour the setting. This is below the level stated above rather than a failure of it, and it is a small fix nobody has made yet.
If something is in your way
Tell me and I will fix it. One person builds this app, so there is no form and no ticket number — an email arrives directly.
It helps to say which screen, what you were trying to do, and what you use to browse — but a sentence saying something does not work is worth far more than nothing, so please do not hold back for want of detail.