Accessibility statement

Our target

We are working towards conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA. We do not yet claim conformance: a full automated and manual audit, including testing with assistive technology users, is still to be completed.

What we have built in

• Semantic HTML, a logical heading structure and a "Skip to main content" link.
• Full keyboard navigation with a clearly visible focus indicator.
• Labelled form fields, error summaries and inline error messages that do not rely on colour alone.
• Status announcements for search results and form outcomes.
• Touch targets of at least 44 × 44 CSS pixels on key controls.
• Respect for your operating system's reduced-motion preference.
• Password managers and pasting are fully supported on sign-in forms.

Colour contrast checks

Calculated contrast ratios for the core palette (WCAG relative luminance):

• Main text #172B3A on white: about 14.6:1 (passes AA).
• Secondary text #526273 on white: about 6.1:1; on #F2F5F9: about 5.7:1 (passes AA).
• White text on primary blue #246BFE buttons: about 4.6:1 (passes AA for normal text).
• Primary blue #246BFE as text on #F2F5F9 is about 4.2:1 and fails AA, so links use the darker #1D55CA (about 6.6:1 on white).
• The border colour #D5DEE8 is below 3:1, so form fields use a darker #6B7C8F border (about 4.4:1) to stay identifiable.
• Error #B42318 on white: about 6.5:1. Success green #2E7D32 on white: about 5.1:1. Community purple #7B3FE4 on white: about 5.7:1.

Personalise your experience

Use the Accessibility button in the header (or press Alt + Shift + A) to increase text size, increase contrast, reduce motion, widen line spacing or switch to a simplified layout. Signed-in users have these preferences saved to their account.

Media

Any video or audio content published on OpenPath must include captions or a transcript.

Feedback

If you find a barrier, please contact us and choose "Accessibility issue". We aim to respond within five working days.