Accessibility statement

• Every task can be done with a keyboard alone, and the element with keyboard focus is always visibly outlined.
• A skip-to-content link is the first thing you reach with Tab on every page, and every page has one main region for it to land on.
• Motion respects the reduced-motion setting: spinners fall back to text rather than animating.
• Colors were chosen against measured contrast ratios, and every text-and-background pairing in the design is checked by an automated test.
• Nothing is revealed by hovering alone. Anything hidden opens on click or tap, which also means it works on a touchscreen.
• On touch devices, buttons and other targets are at least 44 by 44 pixels.
• Status is never carried by color alone — evidence labels, unread counts, and verification badges all say it in words.
• Public pages — profiles, job postings, this page, and the rest of the footer pages — render on the server and work with JavaScript turned off. That includes applying to a job and withdrawing an application.
• Heading order, hover-only tooltips and focus-outline removal are checked by automated tests on every change, so a regression fails the build rather than reaching you.

• The workflow for alt text on images has not been exercised, because there is no surface yet that publishes images. It will be built with the first one, not after.
• A full screen-reader pass across the signed-in flows has not been done. Individual surfaces were built to the rules; the end-to-end listening test is outstanding.
• Form labels are still checked by hand. Heading order, hover-only tooltips, focus-outline removal, and the no-JavaScript rule each have an automated test now; nothing yet reads every input on every page to prove it is labelled.
• Captions and transcripts have no workflow yet, for the same reason as alt text: no media surface exists.

If something here stopped you from doing what you came to do, write to [email protected] and say which page and what happened — the assistive technology and browser you were using helps, but a plain description is enough. A person reads it and replies. A problem with the content of a page, rather than the way the page behaves, goes through report a problem.

Last reviewed 26 Jul 2026.