Keyboard paths
Menus, forms, disclosures, image viewers, and dialogs should have visible focus, a sensible tab order, Escape handling where appropriate, and focus returned to the control that opened a surface.
Accessibility
A site that leaves room for questions.
We aim to make event information and contact paths readable, keyboard-friendly, and useful on the devices families already use. The protected contact form is currently available, and direct email is also supported.
Our commitment
Readable by default, adaptable when needed.
Public pages use Atkinson Hyperlegible for body copy and Fredoka for headings, visible focus states, high-contrast palette tokens, descriptive image text, and interactive targets sized for touch and keyboard use.
Motion choices
We respect reduced motion through the prefers-reduced-motion setting, avoid autoplaying audio, and keep a useful poster or static state when motion is not wanted or cannot start.
Status is not color-only
Event, registration, and live-chat states use readable labels and status text in addition to color. Text alternatives stay available when media or an external panel cannot load.
Contact and chat availability
Support should be safe to use.
The protected contact form is currently available, and direct email is also supported. Public live chat and the Discord reply bridge are not enabled yet, so there is no visitor chat dialog, office-hours queue, or reply path to depend on. If chat is considered in the future, it should provide a labelled dialog, live region, keyboard focus management, safety notice, and under-13 guardian notice before launch.
Please keep unsafe details out of messages
Do not share passwords, home addresses, school schedules, medical information, or emergency requests through the contact form. A parent or guardian can use the form for a child under 13. Use local emergency services for an emergency. Public live chat and the Discord reply bridge are not enabled yet, so there are no visitor chat files, voice/video calls, accounts, Discord invites or usernames, chatbot or AI replies, or response-time promise.
The protected contact form uses a validated server API and keeps messages in a bounded text-only path. No 30-day chat-retention job is running because public chat is not enabled. Direct email remains available when that is easier.
Known limitations
Tell us what got in the way.
Some external forms, embedded media, third-party pages, and older event records may not meet every accessibility need. We cannot promise that every partner-controlled surface will be accessible or available. If a page, event detail, or media item is hard to use, contact us and we will help find a workable path.