Colophon · Access
A door, held open.
A members' club is only a club if its door opens. We design Nexus Club to be navigable by keyboard, legible to screen readers, and readable at the type sizes a working day asks for. Below is what we hold ourselves to, where we currently fall short, and the route to write to us when something blocks you. We answer.
The standard
We hold ourselves to the Web Content Accessibility Guidelines (WCAG) 2.1 at conformance level AA. The standard is not a ceiling — it is a floor we keep checking against, page by page, as the site grows.
What we already do
Every interactive control reaches by keyboard alone. Focus is visible — a violet outline, two pixels, on every focusable element. Motion respects the prefers-reduced-motion operating-system preference; the ambient orbs, breathing buttons, and animated reveals all stop when the system asks them to. Form inputs are labelled, form errors are announced, and headings nest in order.
Type is set at sixteen pixels minimum, with a body line-height generous enough for low-vision reading. Colour contrast against the paper-near-black background is checked at design time — body text exceeds 7:1, accent text clears 4.5:1.
Where we currently fall short
Honesty serves a member better than a clean conformance claim. The known gaps:
- The campaign cover artwork is generated programmatically and does not always carry a meaningful alt description. We are working through the catalogue.
- The command palette (⌘K) is mouse-trivial but keyboard-second-class — arrow-key navigation is in, screen-reader live-region announcements are not yet.
- Some editorial flourishes — the running heads, the dot-leader rules — rely on visual character. They are marked aria-hidden, which removes the noise from screen readers but means the small visual "rest beats" in a page do not reach assistive technology.
We would rather list these in writing than carry a checkmark we have not fully earned.
Writing to us
If something on the site blocks you, write to access@thenexusclub.org. Describe what you were doing, what device and assistive technology you use, and where the block sat. We answer within five business days, and fixes — when small — ship the same week.
What this is, and isn't
This is a standing commitment. It is not a regulatory compliance certificate. We do not engage a third-party auditor for stamps; we do read the WCAG checklist, test with screen readers, and treat reported blocks as bugs of the highest priority.