Accessibility

• Semantic HTML with a logical heading order on every page
• A skip link, and focus moved to the main region after navigation
• Visible focus indicators on every interactive element
• Text and interface colours chosen to meet AA contrast in light and dark appearances
• Form fields with associated labels, hints and error messages, plus an error summary
• Descriptive link text rather than “click here” or bare URLs
• Tables with proper header cells, captions and horizontal scrolling containers
• Images either given meaningful alternative text or marked decorative
• No motion beyond page transitions, and reduced-motion preferences respected
• Layouts that reflow without horizontal page scrolling

• Keyboard-only walkthroughs of the primary journeys
• Automated checks in the build for heading order, labelling and link text
• Contrast values computed against the design tokens rather than sampled by eye

Independent audit and assistive-technology testing across a range of screen readers have not yet been carried out.

• Screen reader testing has been limited, so specific assistive technologies are not listed as verified.
• No independent accessibility audit has been completed.
• The applications have their own accessibility work, reported separately from this page.
• Third-party content is not used on this site today; if any is added it will be assessed before it ships.

• Extending automated checks to cover every page in the build, not a sample
• Arranging assistive-technology testing so specific tools can be listed honestly
• Reviewing documentation pages for reading order and heading structure as they are written

If something on this site or in the products blocks you, please tell us. Reports about accessibility are prioritised, and you do not need to identify the standard involved.