What this site does, and what it does not do yet.

There is no interaction on this site that requires a mouse, a pointer, hover, a gesture or a drag.

• A SKIP TO CONTENT link is the first focusable element in the site header, and jumps past the navigation to the main region.
• Navigation, essay links, the Dispatch field and every control are standard focusable elements in document order.
• On narrow viewports the menu opens as a dialog; Escape closes it and returns focus to the button that opened it, so it is never a dead end.
• Reading and Immersive is exposed as a labelled radio group; both options are reached with Tab and activated with Enter or Space.
• Inside Before You Know, each question is a real fieldset of real radios, and focus moves to the heading of each new stage as the sequence advances.
• The film in Olivia: Exhibit 01 has one ordinary button — play, pause, continue, replay — with a label that changes to match the state.
• Buttons and call-to-action controls are laid out at a minimum height of 44px. Links inside running prose are not, because they sit in the line of text.

A single site-wide rule draws a 1px outline, offset from the element, on anything that receives keyboard focus. It is never removed for aesthetic reasons.

The one control that suppresses the browser default is the Dispatch email field, and it replaces it: the whole field row takes the same outline, plus a signal that concentrates while the row holds focus. Removing the indicator without replacing it does not happen anywhere on this site.

If your system asks for reduced motion, this site listens to that setting rather than offering its own switch to find.

• Entrance animations, drifting elements, drawn rules and progress animations are switched off, not merely shortened.
• Neither film in Olivia: Exhibit 01 autoplays, for any visitor. Each page settles on its composed still, and a film runs only if you press play.
• Under reduced motion the exhibit's construction sequence is delivered as four selected still states instead of a film, so none of its argument is lost.
• The same applies when your browser reports a Save-Data preference.
• Nothing flashes or strobes anywhere on this site, nothing loops continuously, and no animation is required to reach any content. Motion is limited to entrances, transitions and the two films in the exhibit.

Pages are rendered on the server, so the text of every essay, source note and accountability page is present in the HTML before any JavaScript runs.

• Every essay offers Reading mode as well as Immersive: the same manuscript, set as plain type, with the opening photograph not loaded at all.
• Every Season 01 essay has a free public source note, in plain prose, at its /sources address.
• Opening photographs carry written alternative text; purely decorative rules and marks are hidden from assistive technology rather than announced as meaningless.
• A plain-text description of the publication and its public structure is published at /llms.txt.
• Nothing is behind a payment, an account, an email address or an age gate.

An Experience is an editorial demonstration, so its meaning must survive not being able to run it. Each one publishes a binding mechanics register at Examine that states in plain prose what it claims to be, what it does, what it stores and where it stops. That register is a complete written account of the work.

• Before You Know is text only. Its questions, both responses and its result are prose; progress and the moment sources are revealed are also announced to assistive technology.
• When Before You Know cannot run honestly it says so on the page instead of presenting a broken sequence, and it is withdrawn from navigation and from the sitemap at the same time.
• The film in Olivia: Exhibit 01 has no audio track and no speech, so there is nothing to caption. It is not required: the reveal and the debrief that follow it state in writing what the film shows, and the still image beneath the player is described in text.
• No experience uses the camera, the microphone, cursor tracking, face detection or a time limit.

Stating a scope is the only way this page can be checked, so this is the scope rather than an impression of one. Checked by hand on this page, as of 3 September 2026:

• Keyboard-only traversal from the top: the skip link is the first stop, every subsequent stop is reachable with Tab, and each one draws a visible focus outline.
• Layout and reflow at 1440px, 1280px and 390px, with no horizontal scrolling and no element extending past the viewport at any of them.
• Rendered HTML for landmark structure, heading order and text alternatives.
• That this page runs no animation of its own at all, so a reduced-motion preference has nothing to switch off here.

Walked by hand on 3 September 2026, at those three widths and under the same keyboard-only traversal — this page, the four Dispatch outcome pages added since the previous date, and the closed state of a Season 01 letter address:

• /access
• /dispatch/check-your-inbox
• /dispatch/confirmed
• /dispatch/link-expired
• /dispatch/unsubscribed
• a Season 01 letter address opened without its key, which is the only state of it a reader without a Dispatch can reach

On each: one h1 and one main region, headings in order, every stop reachable with Tab and drawing a visible focus indicator, and no element extending past the viewport at any of the three widths. Where a page carries the Dispatch field, the input is labelled, its note is associated with it, and the result is announced through a polite status region. None of them runs an animation that a reduced-motion preference would need to switch off. The letter gate is the exception described in section G: it has no focusable element at all.

Checked automatically, on every release build: that every public route renders with a canonical link, that this page resolves rather than redirecting, that no encoding corruption reaches the published text, and that every public route is either named in the scope above or recorded as deliberately outside it, so a new route cannot leave this section quietly out of date.

Testing was done by the publication, in current Chromium-based browsers, on Windows. That is the whole of the scope: everything not named above is untested. The behaviour described in sections A to E is how the site is built and is held in place by the test suite; it has not each been re-walked by hand for the date on this page.

These are known and are stated here rather than discovered by the person they affect.

• No independent accessibility audit has been carried out, and no WCAG conformance level is claimed or certified.
• No systematic screen-reader test matrix has been run. Semantics, labels and announcements were built and reviewed deliberately, but NVDA, JAWS and VoiceOver have not each been walked through every route.
• The focused shell around Before You Know replaces the site header and carries no skip link. Its first focusable element is the wordmark, and the sequence is a short tab away rather than one keystroke away.
• A Season 01 letter address opened without its key shows one sentence and nothing else: no site header, no navigation, no skip link and no focusable element at all. Nothing is unreachable, because there is nothing there to reach. But it is a closed door rather than a page, and it offers no way onward. That is deliberate, and it is recorded here rather than described as ordinary navigation.
• Reading and Immersive announces itself as a radio group but does not implement arrow-key roving focus, so it behaves like two buttons rather than like a native radio group.
• Testing on macOS, iOS, Android and on Firefox and Safari is outstanding, as is testing with voice control and with switch access.
• The site has one fixed dark palette. There is no light theme, no high-contrast theme, and forced-colours modes have not been verified.
• Some mono labels are set small and in uppercase by design. They are supporting labels rather than body text, but they are harder to read than the prose around them.
• Reading and Immersive is remembered in your browser, so it needs JavaScript and local storage; without either, essays open in Immersive.
• Cognitive-load and plain-language review of the essays themselves has not been done. They are long-form argument and are written as such.
• A full manual keyboard and reduced-motion walkthrough of every public route, dated and repeated at each release, is not yet part of the release process. Section F says what was checked instead.

An accessibility problem is treated exactly like a factual error: it is a defect in the publication, not a special request. Report it through Corrections & Contact, naming the page, what you were using, and what you could not do.

Reports are read by a person and answered by a person. If a fix is not possible quickly, the limitation is added to section G rather than left unsaid.