Current interface provisions
Semantic landmarks, skip navigation, logical headings, visible keyboard focus, labelled forms, native controls, responsive layouts, reduced-motion support, alt text and colour-independent status text.
Accessibility extends beyond the interface
Published resources should use plain language, meaningful link text, structured headings, accessible tables, captions or transcripts, descriptive images and accessible PDF or alternative formats.
Performance is an access requirement
Core content is server rendered, hero content remains meaningful without media, non-critical interaction is limited and layouts work on narrow screens. Future third-party scripts require review.
What still requires formal validation
Screen-reader testing across priority journeys, browser and assistive-technology coverage, PDF standards, form error summaries, multilingual readiness and independent WCAG review.
How accessibility barriers will be handled
A dedicated contact route will request the page or task, device or assistive technology where the user chooses to share it, the barrier and a preferred response format. Urgent access alternatives should be offered where possible.