Accessibility
Accessibility Statement
What we target, what's implemented today, and where we still have work to do.
Our target
We build Fast Elections against the Web Content Accessibility Guidelines (WCAG) 2.1, level AA. That's a target we test against ourselves, not a third-party certification — nobody has audited this site against WCAG and issued us a conformance report. We're telling you what we aim for and, honestly, where we currently fall short.
What's implemented
Keyboard operability. Every ballot control — picking one option, picking several, ranking, and yes/no/abstain motions — can be operated with Tab, Enter, and Space alone, with no mouse required. The full voter flow, from opening a ballot link through confirming and casting it, works keyboard-only.
ARIA roles on ballot controls. Selectable choice cards expose role="radio" or role="checkbox" (grouped under role="radiogroup" or role="group") so screen readers announce them as the controls they are, with aria-checked reflecting selection state.
Reduced motion. Every decorative animation — page reveals, hover transitions, entrance effects — is disabled site-wide for visitors whose system has "reduce motion" turned on (prefers-reduced-motion: reduce).
Visible focus indicators. Interactive elements across the marketing site, the signed-in app, and the ballot show a clear focus outline in brand navy or red when reached by keyboard, so keyboard users can always see where they are.
Semantic headings. Pages use a single top-level heading (h1) per page with nested h2/h3 section headings, so screen-reader users can navigate by heading structure.
Skip links. The first tab stop on the marketing site and the signed-in app is a "Skip to main content" link, letting keyboard users bypass repeated header navigation.
Known limitations
We have not run a screen-reader spot check with Windows Narrator, NVDA, JAWS, or VoiceOver against the ballot or the signed-in app end to end — our internal audit covered keyboard operability, focus management, labeling, and color contrast, but not a full assistive-technology pass. That's on our list, not done.
The ranked-choice ballot control (tap an option to add it to your ranking, reorder with ↑/↓ buttons) has not been screen-reader tested; its buttons are individually labeled but the overall reordering interaction may not be self-explanatory without sight.
Some data tables in the signed-in dashboard (the voter roster, results tables) are dense and have not been evaluated for screen-reader table navigation.
We have not tested against every combination of browser and assistive technology — our checks were run in one evergreen desktop browser.
Tell us about a barrier
If you hit an accessibility barrier anywhere on Fast Elections — as a voter, an organizer, or a visitor — email jason@fastelections.com with what page you were on and what happened. A person reads and answers that address, and accessibility issues are fixed with priority.
Last updated: 2026-08-06. Questions or a barrier to report? Email jason@fastelections.com — we'd rather hear about it than have you struggle in silence.