Tenurable targets WCAG 2.1 AA. These are the numbers from the shipped build rather than an intention.
| What | Ratio | Standard |
|---|---|---|
| Body text on the page | 13.03 to 1 | AAA at every size |
| Muted text on the page | 5.34 to 1 | AA at every size |
| Navy on the page | 10.85 to 1 | AAA at every size |
Body text is 16 pixels and it is never lighter than the muted tone above. Nothing on the site is set in all capitals and nothing relies on a hairline to be read.
A correct answer fills with the course color and takes a tick and the words The answer. A wrong one takes a line through it and the words Your answer. Nothing depends on telling two colors apart.
Keys one to four answer a question. Enter moves to the next step. Every control is reachable by tab and the focus ring is two solid pixels.
Answering announces what you picked and what was correct through a polite live region. The explanation is read in the order it appears.
A tick draws in over 160ms and a fill lands in 120ms. Under prefers-reduced-motion both snap instead.
There is no clock on a question and no penalty for a slow answer. A class waits as long as you do.
Every button and every answer row is at least 44 pixels tall. Most are 48 or more.
An automated check finds about a third of what matters. Tenurable has not yet been tested end to end with a screen reader by someone who uses one daily.
The certificate is a rendered card and it reads correctly as text. A printed copy has not been checked against a screen reader workflow.
A page that fights your setup is a bug and it gets treated as one. Say what you were using and what happened.