Accessibility Statement

Our Commitment

IdentityFirst is committed to ensuring digital accessibility for people with disabilities. We continually improve the user experience for everyone and apply the relevant accessibility standards. Accessibility is not an afterthought — it is built into our design and engineering process from the outset.

Conformance Status

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. The following measures have been implemented across the platform:

• Keyboard navigation — every interactive element is reachable and operable without a mouse
• Skip-to-content link — available at the top of every page for keyboard and screen reader users
• ARIA labels and landmarks — applied to navigation, main content, complementary, and form regions
• Colour contrast — text-to-background ratios of at least 4.5:1 for normal text and 3:1 for large text
• Focus-visible outlines — a clearly visible focus ring is shown on all interactive elements
• Screen reader announcements — live regions announce state changes (e.g. form submission results, navigation updates)
• Semantic HTML5 — headings, lists, tables, and landmarks used correctly throughout
• Alternative text — all meaningful images carry descriptive alt text; decorative images are marked with alt=""

Known Limitations

Despite our best efforts, the following limitations are currently known:

• Mobile menu focus trap — uses the HTML inert attribute to prevent background content from receiving focus while the menu is open. This attribute is supported in all modern browsers since 2023. Users on legacy browsers may experience reduced focus management. We recommend Chrome 105+, Firefox 112+, or Safari 15.4+.
• Complex data visualisations — some charts in the platform application provide visual context that is difficult to fully convey with text alone. We provide tabular data alternatives and descriptive summaries alongside each visualisation.
• Third-party embeds — certain third-party widgets (e.g. calendar booking, live chat) are outside our direct control. We review vendor accessibility commitments at renewal and flag known issues to partners.

Testing Approach

We take a layered approach to accessibility testing:

• Automated scanning — pages are tested with axe-core via Playwright end-to-end tests on every pull request. Builds fail if new violations are introduced.
• Manual testing — keyboard-only navigation and VoiceOver (macOS) testing is performed quarterly on representative user journeys, including sign-in, navigation, and form submission flows.
• Design review — colour contrast and touch-target sizes are verified during design handoff using our design token system.

Feedback & Reporting Barriers

If you experience any accessibility barrier on our website or platform, please let us know. Your feedback helps us improve.

Enforcement Procedure

If you are not satisfied with our response to your accessibility report, you may contact the Equality Advisory and Support Service (EASS), which provides free advice and assistance on the Equality Act 2010 in Great Britain.

Statement Date

This accessibility statement was last reviewed in February 2026. We review this statement at least once a year and following any significant changes to the site.