Keyboard-friendly paths
Interactive controls should remain reachable without a pointer, with visible focus states and predictable navigation order.
Access for more people
A calmer interface should be an accessible one.
We design AIHire with semantic structure, readable contrast, clear status language, and responsive interaction in mind. Accessibility is ongoing work, not a one-time claim.
Clear structure
Pages use headings, labels, landmarks, responsive layouts, and explicit empty or error states to reduce cognitive load.
Understandable status
Loading, success, warning, unavailable, and failure states are written out instead of relying on color alone.
If something blocks you
Tell us which page, control, browser, assistive technology, or file format caused the issue. Include the outcome you expected, but never include private applicant content in a report.
Supported alternatives
If a document preview is not usable, the product provides text-based evidence and direct report links where available. Contact support if a required format still cannot be accessed.
Need an accessibility adjustment?
Contact support with a safe description of the barrier. We will use the report to improve the experience and help with an available alternative.