Accessibility at CareerPaths
Last reviewed: 10 September 2026
1 · What we're aiming for
We build to WCAG 2.2 Level AA as our target standard. That applies to this website, to Career Visibility Software, and to the careers websites and interactive tools we build for clients.
We describe it as a target rather than a guarantee, deliberately. Accessibility is not a state you reach once. It depends on the content published after a site goes live — the headings people write, the images they upload, the documents they attach — and most of that is added by the people who own the site, not by us. A vendor claiming permanent conformance across content they don't control is claiming something they can't know.
What we can tell you is what we build to, what we've tested, what we know is imperfect, and how to tell us when we've got it wrong. All four are below.
2 · What we do
In how we build. Semantic structure so screen readers can navigate by heading and landmark. Keyboard access to everything you can reach with a mouse, with a visible focus indicator. Colour contrast checked against AA thresholds. Form fields with real labels, and errors that say what went wrong in words. Motion that respects a reduced-motion preference. Text that reflows on a phone without a horizontal scrollbar.
In our interactive work. Career maps, explorers and animated scenes are the hardest things we make to get right, because they are visual by nature. Where an interaction can't be made fully equivalent, we provide the same information another way — a list view alongside a map, text alternatives for scenes — rather than leaving anyone without a route to the content.
In what we hand over. Clients can edit their own sites. We give them guidance on the things that most often break accessibility after launch: image descriptions, heading order, link text that makes sense on its own, and PDFs.
3 · Where we currently fall short
We have not yet completed a full independent audit, so this section does not list findings yet. When it runs, this statement will be updated with what it finds — including the items we have not fixed.
If you have hit a barrier we haven't listed, section 5 is how to tell us. We would rather know.
4. If you're a public sector organisation
This matters more than the rest of this page, so it's worth being precise.
The Public Sector Bodies (Websites and Mobile Applications) Accessibility Regulations 2018 apply to you, not to us. If we build a careers website for an NHS body, a local authority, a university or another public sector organisation, that website falls within your regulatory duty — and the legal responsibility for it stays with you.
What that means in practice:
You need your own accessibility statement for the site, in the model format the regulations require. It is not the same as this document, and it has to name the site, the standard, the known barriers and the enforcement route
You need it published from the day the site goes live, and reviewed at least annually
We will help you produce it. We know what we built, and we can tell you what we tested and what we know is imperfect — which is most of the content the statement needs
We can arrange an independent audit of your site as a separate engagement, and we'd recommend it before launch rather than after
We would rather raise this at the start than have it arrive from your compliance team three weeks before go-live.
5 · Everyone else — the Equality Act
Outside the public sector, the Equality Act 2010 still requires reasonable adjustments so disabled people aren't put at a substantial disadvantage. A careers website that a screen reader user can't navigate is a barrier to applying for a job, which is exactly the kind of disadvantage the Act is concerned with.
Building to WCAG 2.2 AA is how we help you meet that, and it's why the target applies to every site we build rather than only the ones legally obliged to hit it.
6 · Tell us when we get it wrong
If you can't use part of this site, or a site we built, tell us:
We'll acknowledge within one business day and tell you what we can do and when. If you need information in another format — large print, plain text, a different document type — ask and we'll provide it.
If you're not satisfied with our response, in the UK the Equality Advisory and Support Service (EASS) handles accessibility complaints: equalityadvisoryservice.com. For a public sector website, the enforcement body is the Equality and Human Rights Commission.
7 · How this statement is maintained
Reviewed at least once a year, and whenever we make a significant change to a product. The date at the top is when it was last revised.