🎉 Limited-time offer — Save 15% on annual RPO plans booked this quarter. See pricing →

Login Request a Demo

Home/Legal/Accessibility Statement

Legal

Accessibility Statement

Last updated: August 2026

Placeholder legal content. This page is a template written for a prototype build — it has not been drafted or reviewed by qualified counsel or an accessibility specialist. Replace it with a real, audited statement before this site goes live.

1. Our commitment

EMPLOYAI is built to work for employers and candidates alike, which includes people using assistive technology, keyboard-only navigation, or browser accessibility settings like reduced motion and larger text. Accessibility has been treated as part of the design system from the start, not an afterthought bolted on later.

2. Conformance target

We're targeting WCAG 2.1 Level AA across the site. That's the standard we build against, not yet a claim of full conformance — see the known limitations below.

3. What's built in today

  • Semantic landmarks on every page (header, nav, main, footer) and a "skip to content" link.
  • Visible focus states throughout, including inside the mega menus, mobile drawer, and form controls.
  • ARIA attributes on interactive components — the mega-menu triggers, the mobile drawer, tabbed sections, and the FAQ accordions.
  • Form fields with associated labels and inline, readable error messaging rather than color alone.
  • prefers-reduced-motion is respected — decorative animations are neutralized for users who request reduced motion.

4. Known limitations

In the interest of being honest rather than aspirational, here's what hasn't happened yet:

  • This site has not yet been through a full automated accessibility audit (such as axe or Lighthouse) or manual screen-reader testing.
  • Color contrast has been designed carefully but not independently verified against every state and component combination.
  • Some interactive patterns (mega menus, tabs) have been built with ARIA best practices in mind but haven't been validated with real assistive-technology users.

Closing these gaps — a proper audit, and testing with real screen-reader users — is planned work before this moves from prototype to production.

5. Feedback

If you run into an accessibility barrier anywhere on this site, we want to know about it. Reach out through our Contact page and describe the issue, the page it happened on, and the assistive technology or browser you were using if relevant.