Built to be used
by everyone.
We want anyone to be able to learn about First AI Employee and get in touch, whatever device or assistive technology they use. We aim to conform to WCAG 2.2 Level AA. That is the current version the W3C recommends, and the benchmark that US ADA guidance and the EU's EN 301 549 point to. We test with automated and manual checks and fix what we find, but we don't claim that every page and feature fully conforms.
What we've done
The measures already in place across the site.
Real structure, and a way to skip the menu.
The site is built with proper HTML landmarks (header, navigation, main content, and footer) so assistive technology can move through a page by region. A “Skip to main content” link is the first thing a keyboard user reaches on every page, so nobody has to tab through the whole menu to get to the content.
Works with a keyboard, and shows where you are.
Every link, button, and form field can be reached and used with the keyboard alone, and whatever you are focused on shows a clear outline. Menus and dialogs close with the Escape key.
Honors “reduce motion.”
If your device is set to reduce motion, animations across the site, including the scrolling strip of industries and the small demo effects, are stilled.
Forms that are labeled and speak up.
Our contact and sign-up/onboarding forms have real labels tied to each field, mark required fields so a screen reader announces them (not just a visual asterisk), tell your browser what it can autofill, and announce “sent” and error messages instead of changing silently.
Results that announce themselves.
When an interactive tool recalculates (the cost calculators, the greeting and message generators, the article filters), the new result is announced to screen readers through a live region, and “copied to clipboard” confirmations are spoken too.
Menus that match how they behave.
The header drop-downs are exposed to assistive technology as a button that expands a short list of links, which is what they actually are, so what a screen reader announces lines up with how the menu really works.
Text you can read.
We aim for text and essential controls that meet the WCAG AA contrast minimum against their background, including the illustrated “before / after” cards and the demo text-message panel on the home page.
Where our testing stops.
We would rather tell you plainly than pretend the site is perfect. The automated check described below has a defined edge, and this is where it ends. If something on this site gets in your way, tell us and we'll fix it.
- One page per template. The automated run checks a representative page for each page template, not every URL on the site, so a one-off problem inside a single article or industry page can sit unnoticed until the next manual pass.
- English, at desktop width. The automated run measures the English pages in a 1280-pixel window. The Spanish pages under /es/ and narrow screens are checked by hand.
- The signed-in app is checked by hand. The dashboard, sign-up and onboarding screens sit behind a login and are not part of the automated run. We review them ourselves, which means they get less coverage than the public pages.
- Automated testing only reaches part of the standard. Software can flag a missing label or a weak contrast ratio. It cannot tell you whether link text makes sense out of context, whether a heading order tells the right story, or whether an error message actually helps. Those are human calls, and we can miss things.
Run into a barrier? Tell a real person.
If any part of this site is hard to use, or you need information in a different format, reach out and we'll help you directly and get it fixed. We reply within one business day, usually within a few hours. Please include the page and what got in your way.
Write to us at that address, or call and talk to us. Prefer the phone? That works for anything on this site.
How we assessed this. We check the site with axe-core, run in a headless Chromium browser against the same production build that goes live, on one representative page for every page template in our sitemap: home, pricing, an article, an industry page, an add-on, a calculator, the legal pages, and the rest. It applies the WCAG 2.0, 2.1 and 2.2 Level A and AA rules, and because it runs in a real browser it measures rendered color contrast rather than guessing at it from the markup. Nothing here is scheduled or automatic: we run the check by hand before we publish, and it fails on any violation at all. The last run reported none. Automated testing only reaches part of the standard, so we pair it with a manual review of the site's code and with keyboard and 320-pixel reflow checks, measured against WCAG 2.2 Level AA. This is our own assessment, not a third-party certification. Last reviewed July 27, 2026; we update this page as the site changes.