Skip to content
Centuries Untold

Site

Accessibility

We aim at WCAG 2.2 level AA. This page says what is done, what is enforced automatically, and what is not finished.

Colour and contrast

The palette is defined once and checked by an automated test. Every text colour on every background it appears on is asserted to clear 4.5 to 1, and every control boundary and focus ring to clear 3 to 1. A change that breaks one of those fails the build rather than shipping.

Colour is never the only carrier of meaning. Source tiers, moderation states, and errors all carry a text label as well as a colour.

Keyboard

Everything interactive is reachable and operable from the keyboard. A skip link is the first thing in the tab order on every page.

Focus is always visible: the outline is a global rule, so a new component gets one by default rather than by someone remembering.

Screen readers

Pages use real landmarks and a single ordered heading structure. Forms label their fields and announce errors and success in a live region rather than only changing colour.

The animated heading on the front page exposes its full text as a single label, so it is announced as one heading and not as thirty-one letters.

Motion

The site has a small amount of motion: the front page heading types itself in, the banner drifts slowly, and pages fade up as they arrive.

All of it is switched off by the reduced-motion setting in your operating system. When it is off, every animated element is shown in its finished state immediately, not part way through.

Text and zoom

Text is set in relative units and reflows to 400 per cent zoom without a horizontal scrollbar. Wide content such as a table or a code block scrolls inside its own box rather than moving the page.

Form controls on touch devices are at least 16 pixels, which stops iOS zooming in on a focused field and never zooming back out.

Known gaps

Being specific about this is more useful than a blanket claim of conformance.

  • Digitised documents come from third-party archives as page scans. Where an archive provides no transcription, the images have no text alternative that we can generate honestly, and the page says the text is unavailable rather than inventing a description.
  • Automated end-to-end accessibility testing is not yet part of the build. The contrast checks are; the rest is manual.
  • Some catalogue metadata arrives in a language the surrounding page is not declared in, which can cause a screen reader to read it in the wrong voice.

Tell us

If something here blocks you, write to contact@centuriesuntold.com with the page and what happened. Access problems are treated as bugs, not as requests.