Our target
PairSkill aims to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, the standard behind EN 301 549 and the European Accessibility Act. PairSkill is partially conformant: most of the service meets the standard, with the exceptions listed below.
How we check
Every release runs automated axe checks on twelve key pages (landing, pricing, roles, sign-up, Today, the feed, matches, roles and pools) in light and dark mode, on a phone and a desktop screen, and fails on any serious issue. Our code is also linted for accessibility. We test the same flows with a keyboard only, at 320 px width and at 200% zoom, and spot-check them with VoiceOver and NVDA.
What we have done
Text and controls meet a 4.5:1 contrast ratio in both themes, and form fields have visible 3:1 edges. Every control shows a clear focus ring. Tabs, segmented controls and choice chips work with the arrow keys. Icon-only buttons have names, and the tab bar names include unread counts. Saves, filter results and wizard steps are announced to screen readers. Every page has a skip link, and motion is reduced when your device asks for it.
Known limitations
Skill checks are timed (90 seconds for 6 questions), because the time limit is part of what they measure. If you need more time because of a disability, email us and we will arrange an adjusted check. German, French, Polish, Slovak and Spanish are machine translations in beta and may read awkwardly. The PDF passport uses your browser's print dialog, so its accessibility depends on your browser. Content added by employers and candidates (role descriptions, work samples) may not meet the standard.
Feedback and help
If something doesn't work for you, or you need information in another format, write to hello@pairskill.com. We reply within 5 working days and fix blocking issues as a priority.
Enforcement
If you're not satisfied with our answer, you can contact the authority that oversees accessibility in your country.