Inviqa’s accessibility statement

LAST UPDATED

April 2026

Our commitment to accessibility

Accessibility is a core part of inclusion – and it’s key to designing successful digital products.

Here at Inviqa we commit to doing everything we can to ensure that the products and services we deliver are accessible to everyone – including the more than 1 in 5 people in the UK who experience disabilities.

We aim for WCAG 2.2 AA compliance on all projects, and we consider the needs of disabled people at all stages of the project lifecycle.

We’re proud to have internal accessibility experts within each of our delivery teams.

These knowledgeable individuals help us drive better human and business outcomes through purposeful and inclusive digital products.

All Inviqans benefit from the accessibility resources, checklists, and training we’ve developed in house.

We’re also long-term partners with Dig Inclusion, an organisation dedicated to providing testing, consultancy, and training to diverse businesses.

We work with People for Research, partnering to find diverse participants – including those with digital access needs – for user research and testing.

Our ongoing focus on website accessibility

During our recent update of the Inviqa website, accessibility remained a key consideration. The website was designed with WCAG 2.2 adherence, but accessibility is a process of ongoing improvement and refinement.

We know that our site still has some accessibility problems, and we’re working to address these as soon as possible, with an initial focus on the likes of:

Identifying and rectifying issues around focus states
Improving the accessibility of carousels
Improving the navigation for users of assistive tech – keyboard navigation, screen readers, or something else
Identifying and rectifying images that may be missing alternative text

We’ll continue to test and refine our site going forward, but if you experience any accessibility issues when using the site, please do let us know using our website contact form.

This accessibility statement was last updated in April 2026