Accessibility
Propounded aims to meet WCAG 2.2 at level AA. Rather than claim that once and leave it, the claims below are checked by an automated suite that runs against the built site, and a failure stops the release.
Last revised 19 August 2026.
What is checked before release
- Contrast. Every rendered text node is measured against the background actually composited behind it, not against the colour a stylesheet nominally declares. Anything below the AA threshold fails the build.
- Target size. No interactive control is smaller than 24 by 24 CSS pixels, the minimum in WCAG 2.2 success criterion 2.5.8.
- Keyboard order. The skip link is the first thing the Tab key reaches on every page, and focus is always visible where it lands.
- Structure. Each page has exactly one
h1and no skipped heading level, so a screen reader's outline matches what the page looks like. - Layout. Nothing overflows horizontally from a 320-pixel-wide screen upward, so text reflows instead of forcing a sideways scroll.
- Without JavaScript. The messages themselves render and remain readable with scripting off. Controls that genuinely need scripting are hidden rather than left inert, so nothing you can reach does nothing when you press it.
- Console. No page emits a console error, which is how broken behavior usually announces itself first.
Design decisions that follow from it
Copying a message announces itself to assistive technology through a live region, so confirmation is not carried by a visual flash alone. Motion is opt-out at the system level: with prefers-reduced-motion set, reveal and hover animations do not run.
The site sets no inline styles anywhere, which means it can serve a strict content security policy without weakening it, and it also means a user stylesheet or a reading-mode extension can override the presentation cleanly.
Text is never used as an image, colour is never the only carrier of meaning, and the archive is readable end to end without ever opening a dialog.
What this page does not claim
Automated checking finds the failures a machine can see. It does not replace testing with real assistive technology, and no independent third-party audit or certification has been carried out. Treat the list above as what is verified, not as a guarantee that nothing is wrong.
If something here is hard to use with your setup, that is a defect worth reporting. Note the page, the browser, and the assistive technology involved, and it can be fixed.