Accessible operation and communication
Accessibility is part of the task: a speaker must be able to submit, an organiser must be able to recover from an error and an attendee must understand published information.
Configuration and content
Write recognisable titles and descriptive links. Use headings in a logical order and describe meaningful images. Do not communicate essential information only through colour, an icon or a screenshot.
State dates, time zones, languages and required actions explicitly. Identify fallback languages. A complete default-language text is not the same as a reviewed translation.
Acceptance testing
Complete the key journey using only a keyboard. Check visible focus, sensible order, labelled fields and error messages associated with the correct control. Then test mobile, zoom and longer text.
Automated frontend tests inspect aspects such as accessible names, roles and relationships. They do not automatically establish colour contrast, actual focus order, touch targets, reflow or complete WCAG conformance.
This handbook
The site includes a skip link, keyboard-operable menu, per-language search and image alternative text. Screenshots supplement the instructions; actions also appear in Markdown text. Open an image at original resolution to inspect it.
The language switch preserves the topic. Use printing for a local working copy, but always check the source page’s version and review date for operational use.