Luminid · Legal Entity ID: 3102-950-241 · Costa Rica · hello@luminid.org

Accessibility Statement

Last updated: 2026-07-12

Contents

1. Our commitment 2. What we have built 3. Assessments and accommodations 4. Known limitations 5. Feedback and contact 6. Ongoing work

1. Our commitment

Luminid's mission is to make the job market fairer for everyone. That has to include people who use assistive technology, or the mission fails at the front door.

We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, across the platform. We are not fully there yet, and this page says so plainly. What we will not do is claim conformance we have not verified.

2. What we have built

Accessibility measures currently in place across the platform:

Text contrast of at least 4.5:1 against its background on product surfaces
A visible focus indicator on every interactive element, applied globally
Touch targets of at least 44 by 44 pixels on interactive controls
Full keyboard operability for core flows: sign up, profile, taking a simulation, applying, and reviewing applicants
Semantic landmarks (header, navigation, main, footer) and a logical heading order on new surfaces
Programmatically labeled form fields, with errors announced next to the field they belong to
Status updates for asynchronous results (such as a simulation score arriving) exposed to screen readers via live regions
Motion is reduced automatically for users whose system requests reduced motion; no content flashes
The interface is bilingual (English and Spanish) with the page language declared for assistive technology

3. Assessments and accommodations

Simulations are the core of Luminid, so they carry the strongest obligation.

If you need an adjustment to take a simulation, you can request an accommodation. Voice simulations include a built-in accommodation request path before the call starts, for example if speaking on a live call is not accessible to you. For any simulation, you can also write to hello@luminid.org with the subject line "Accommodation request" and describe what you need, such as extended time or an alternative format.

Requesting or using an accommodation never appears on your profile, never affects your score, and is never shared with employers.

4. Known limitations

Stated honestly, these are the gaps we know about today:

We have not yet completed an independent third-party accessibility audit of the full platform. Our conformance target is self-assessed
Exported resume PDFs have limited semantic tagging, so screen reader support in exported documents is weaker than on the equivalent web pages
Some data-dense employer surfaces, such as pipeline boards and comparison views, are keyboard operable but slow to traverse with a screen reader, and some charts lack complete text alternatives
Older pages built before our current design system may have inconsistent heading structure or contrast in places we have not yet reworked
Content written by employers, such as job descriptions, is outside our direct control and may not meet the standards this page commits to
Live voice simulations are inherently audio-based; the accommodation path in Section 3 exists precisely because of that

We list these to be held to fixing them, and this section shrinks as they are fixed.

5. Feedback and contact

If you hit a barrier anywhere on Luminid, tell us. Write to hello@luminid.org with the subject line "Accessibility". Include the page, what you were trying to do, and the assistive technology you were using if any.

We acknowledge accessibility reports within five business days. Barriers that block a core flow (signing up, taking a simulation, applying) are treated at the same priority as functional outages.

6. Ongoing work

Accessibility review is part of our release checklist for new surfaces, covering contrast, focus, keyboard paths, labels, and live regions. We test with keyboard-only navigation and screen readers on the flows we ship. An independent audit is planned as the platform stabilizes, and its findings will update both the platform and this page.

This statement was last reviewed on the date shown at the top of this page.