Accessibility target
Our engineering target is WCAG 2.2 Level AA. WCAG organises accessibility around content being perceivable, operable, understandable, and robust. This target is a continuing product requirement, not a claim that every page, third-party component, or editor-created item has completed an independent conformance audit.
Measures built into the website
- Semantic landmarks, headings, links, buttons, lists, forms, labels, and status messages.
- Keyboard-operable navigation, dialogs, popup focus management, dashboard actions, and rich-editor controls.
- Visible focus feedback, minimum interactive target sizing, direct Light/Dark switching, and system-colour preference on first visit.
- Responsive layouts designed for desktop, tablet, zoomed views, and narrow mobile screens without intentional horizontal scrolling.
- Reduced-motion support for non-essential animation.
- Alternative-text inputs, captions, native audio/video controls, and click-to-load consent for third-party embeds.
- Descriptive validation errors, live status announcements, and fail-closed human verification for public forms.
Content-editor responsibilities
The dashboard permits rich text, images, galleries, audio, video, and embeds. Administrators should use meaningful heading order, descriptive link text, useful alternative text, captions or transcripts where appropriate, and avoid placing essential information only inside an image or video.
Known limitations
- Editor-created content can be less accessible when alternative text, captions, heading structure, or descriptive link labels are omitted.
- Third-party players and embedded services have accessibility characteristics controlled by their providers.
- Automated checks cannot detect every accessibility barrier; keyboard, zoom, contrast, mobile, and assistive-technology testing must continue as templates and content change.
- Very long email addresses, URLs, code, and third-party content may require wrapping or horizontal scrolling inside their own bounded component.
Compatibility and testing
The site is designed for current standards-based browsers and responsive devices. Release checks should cover keyboard-only operation, 200% and 400% zoom, narrow mobile widths, Light and Dark themes, reduced motion, form errors, focus order, screen-reader announcements, and representative rich-media content.
Feedback and alternative formats
Report an accessibility barrier through the contact page. Include the page, the task you were trying to complete, your browser or assistive technology where comfortable, and the adjustment or alternative format that would help. We will assess the report and aim to provide a practical response.
Review
This statement should be reviewed after major navigation, dashboard, form, rich-editor, media, or template changes and after any formal accessibility assessment.