Accessibility statement

1. Our commitment

Labradoor is a platform students use to find research work and labs use to hire. If any part of it is unusable for you, that is a barrier to work and education, not a cosmetic problem. We treat it that way.

We aim to meet WCAG 2.1 level AA. We are partially conformant: most of the platform has been measured against that standard and meets it, and the parts that have not are listed in section 3 rather than left unsaid.

2. What we have measured and fixed

These were checked programmatically across the student, researcher and company areas of the platform, in both light and dark appearance:

• Text contrast (1.4.3). Every text colour is measured against the surface actually behind it, including transparency, and meets 4.5:1, or 3:1 where the text is large.
• Control boundaries (1.4.11). Form field borders and other interface edges meet 3:1 against their background, so an input is visible as an input.
• Visible focus (2.4.7). Everything reachable by keyboard shows a focus indicator, so you can see where you are without a mouse.
• Reduced motion (2.3.3). If your system asks for reduced motion, page entrance animations resolve immediately.
• Names and roles (4.1.2). Dialogs, expandable panels and filter groups use native elements or the matching ARIA roles, so a screen reader announces what they are and whether they are open.

3. Known problems

We would rather tell you what is broken than claim it is not. As of the date above:

• We have not tested with real screen readers. Our checks are automated, and automated checks cannot tell you whether a page makes sense when read aloud. This is the largest gap.
• Some third-party steps are outside our control. Card payments are handled by Stripe and file uploads by Supabase, on their own interfaces.
• No independent audit has been carried out. Nothing here has been verified by a third party.

4. Telling us about a problem

If something blocks you, email boyuanl6@ucla.edu. It helps if you can say which page you were on, what you were trying to do, and what you use to browse — a screen reader, keyboard only, magnification, and so on. You do not need to know the technical cause.

We aim to reply within five working days. If a barrier stops you completing something time-sensitive, such as a job application before its deadline, say so and we will help you complete it another way while we fix the underlying problem.

5. This statement

Prepared on 24 September 2026, based on our own testing of the live platform. We review it when the interface changes materially. Related: Terms of service and Privacy policy.