How this site is built
Accessibility.
This site is for people with disability, including people who are blind or have low vision, so it being usable isn't a feature. It's the whole thing.
What we're aiming at
WCAG 2.2 Level AA, and past it where the standard is a floor rather than a goal. Meeting AA is not the same as being easy to use, and the second one is what we're actually after.
What that means here
A typeface drawn for this
Atkinson Hyperlegible throughout, drawn by the Braille Institute so letters that normally blur into each other stay distinct.
Text that actually scales
The size control scales every size on the page — headings, buttons, labels — not just body copy. Line and letter spacing too.
Three themes, not two
Light, dark, and a real high-contrast mode that drops the mid-tones rather than just darkening the background.
Never colour alone
Anything shown in a colour is also shown with a word, an icon or a shape, so nothing depends on telling gold from navy.
Targets you can hit
Every interactive target is at least 44 by 44 pixels, which is larger than the standard requires.
Forms without JavaScript
Every form works with scripting off. Errors arrive as real page content in a labelled alert, not a tooltip that vanishes.
Descriptions are mandatory
Every photo needs a written description before it can be published. A photo nobody can describe is one half this audience can't use.
A real outline
Headings are properly nested and landmarks are real, so skipping through a page by heading gets you a sensible outline.
Said out loud
What isn't right yet
Listing these is more useful than claiming they don't exist.
- Most venues have very little confirmed about them. Every venue page says how much has been checked, but it does mean the site is more useful in some suburbs than others.
- The map is a visual extra. Every pin on it is in the list beside it with the same information, so nothing is reachable only by map — but the map itself is not usable by keyboard or screen reader.
- The site hasn't been through a formal audit by anyone other than the people who built it. Worth knowing when you read the paragraph above about WCAG.
Tell us when it fails.
If something here is hard to use, or impossible, that's a bug and we'd rather hear about it. Say what you were trying to do, what happened, and what you were using — a screen reader and its version, magnification, keyboard only, whatever applies. That last part usually saves a week of guessing.