Quoroom.org

Quoroom.org

Accessibility

This site is about elections, and an election nobody can take part in is the problem it exists to describe. The same standard applies to the site itself. Below is what it does, measured rather than claimed, and what it is known not to do yet.

Target WCAG 2.2 level AA Status substantially conformant, self-assessed Formal audit none yet Last assessed 2026-10-10

Self-assessed, and we say so

No independent auditor has reviewed this site, and no automated tool's score is reported here as if it were one. What follows is our own assessment, with the measurements that back it and the gaps we have not closed. We will update it when either changes.

What the site does

It reads without JavaScript

Every page is a static document. A short script on every page applies the light or dark theme you chose before the page paints, and on every page except the request and claim forms a second one loads Google Tag Manager, described on the privacy page. Without the first, the theme follows your system setting and the theme switch stays hidden; nothing depends on the second. In the register, the search field, the map highlighting and the PNG download of a QR code are added by script; without it the county and A–Z pages, plain links and the SVG version do the same jobs. The deadline calculator needs JavaScript to calculate, and the statutory deadlines it computes are written out in the text of the pages it links to. The request forms need JavaScript to send.

It is operable from the keyboard

Every page starts with a skip to content link that is the first thing the Tab key reaches. Focus is always visible: a 2.5 px outline, offset from the element, on every link, button, field and control.

It is structured, not just styled

One <h1> per page and headings that descend in order; a single <main> landmark on every page; real tables with header cells, not grids of divs; lists marked up as lists; and the language declared on every page — including the Spanish ones, which also mark the English-language statutory text inside them as English so a screen reader switches voice rather than reading English with Spanish phonemes.

Contrast is measured, not eyeballed

Every text colour was computed against the surface behind it, in both the light and the dark theme. The results:

TextLight themeDark themeAA needs
Headings15.5 : 115.4 : 14.5 : 1
Body text11.3 : 111.0 : 14.5 : 1
Secondary text5.6 : 16.4 : 14.5 : 1
Small labels4.8 : 14.7 : 14.5 : 1
Links in text5.1 : 17.5 : 14.5 : 1
Primary button4.7 : 19.2 : 14.5 : 1

The numbers are measured against the surface each colour actually sits on, which on this site is often not white: statute blocks, callouts and the footer sit on a tint, and a subdivision you link to highlights onto a warmer one. Those surfaces are the binding constraint, and meeting them leaves little room between the two greys — so the step between secondary text and small labels is carried by size and weight rather than by a paler colour that would fall under the threshold.

Four of those rows were failures at some point, and all four were found by measuring rather than by looking:

The bright brand orange is kept for rules, bars and underlines, where 3 : 1 on a non-text element is the requirement. The check that produced this is a sweep over every text node on 20 pages in both themes, resolving each element's real background through its ancestors: 3,788 nodes, no failures.

It respects what your system asks for

The theme follows your operating system's light or dark setting, with both palettes designed rather than inverted. prefers-reduced-motion turns off every transition. Text is set in relative units and the layout reflows to a single column, so browser zoom and larger default text sizes work instead of breaking it. Nothing on the site flashes, auto-plays, moves on its own, or imposes a time limit.

It loads from one place, with one exception

The fonts, styles and scripts are served from this site. The one exception is Google Tag Manager, which every page except the request and claim forms requests from googletagmanager.com as it opens. It loads in the background and nothing on the site depends on it, so a page reads and works the same when that request is slow, blocked or fails — which is an accessibility property as well as a privacy one, on a slow or filtered connection.

What falls short

Listed because a statement that claims no gaps is not credible.

  1. No independent audit. Everything above is self-assessed. We have not had a screen-reader user test the site, and that is the test that matters most.
  2. Long statutory blocks have no internal navigation. Section § 5110 runs to dozens of subdivisions. Each has an anchor, but there is no table of contents at the top of the block, so reaching subdivision (c)(4)(B) by keyboard or screen reader means travelling through everything before it.
  3. The deadline calculator is a visual layout. Its rows are a CSS grid, read in source order, which is sensible but is not announced as a table with headers. A screen reader gets the numbers without the column meanings.
  4. Comparison tables scroll sideways on a phone. That is better than crushing them, but a narrow screen still means horizontal scrolling to read a row.
  5. Plain-language. The commentary is written as clearly as we can manage, but it describes statutes and in places it reads like it. WCAG does not require a reading-level ceiling at AA; we mention it because it is a real barrier regardless.

If something here does not work for you

Write to privacy@quoroom.org. Tell us the page and what happened — the assistive technology and browser help, but tell us even if you do not know them.

We will reply within five business days, say whether we can fix it and when, and if we cannot fix it quickly we will get you the information another way in the meantime. If you need any page on this site in another format, ask and we will produce one.

Related