Keyboard navigation
Skip navigation, visible focus states, labelled controls and keyboard-accessible menus and accordions.
Accessibility
The MVP targets WCAG 2.2 AA where practical, with semantic structure, keyboard support, readable responsive layouts and reduced-motion support. A full audit should follow deployment.

What is built in
Accessibility is part of the page structure, the content and the interaction design. It is not limited to a separate accessibility page.
Skip navigation, visible focus states, labelled controls and keyboard-accessible menus and accordions.
Semantic headings, clear landmarks, useful link text and layouts that remain understandable at different sizes.
Animations and smooth scrolling respond to visitors who prefer reduced motion.
Buttons, links and mobile actions use clear targets and feedback for everyday interactions.
How to use the site
Use the skip link to move directly to the main content.
Use the keyboard to move through links, buttons and form fields.
Turn on reduced motion in your operating system or browser if needed.
Call or email the team if a digital route is not comfortable or practical.
Keep improving
The next step is a full accessibility review across browsers, assistive technology, keyboard-only journeys, contrast, forms and the client’s final content.
Report a problem