Accessibility

We want this site to work for everyone, including people who use screen readers, keyboard navigation, magnification, or voice control. This page says what we have tested and where we still fall short.

What we are aiming for

We build toward WCAG 2.2 Level AA. We are not claiming full conformance, because we have not done the testing that claim would require. What follows is what we have actually verified.

What we have tested

• Every link and button we sampled could be reached with the Tab key and showed a visible focus ring when we landed on it. We checked a sample, not all 186, so we say sample rather than every.
• A skip link is the first thing in the tab order, so you can jump past the navigation on every page.
• Text colour was measured on every page that existed at the last full review (fourteen at the time; the site has since grown to twenty-two, and the newer case-study pages use the same components and colour system as the measured ones). That review covered 711 pieces of text. For 408 of them our tooling could work out exactly what colour sits behind the text, and all 408 meet the standard. Where our brand blue and teal did not meet the threshold at small sizes we darkened them, and where a panel is tinted enough to eat that margin it gets its own darker set rather than being assumed to pass.
• Headings run in order with a single top-level heading per page, images carry alternative text, and every link and button has a name a screen reader can announce.

Where we still fall short

• We have not completed a screen reader pass. Our checks are automated and keyboard-based. Automated tooling catches a minority of real accessibility problems, and we are not pretending otherwise.
• The remaining 303 pieces of text could not be measured automatically. They sit over gradients, over layers that overlap each other, or over photographs: backgrounds our tooling will not guess at, and it is right not to. We checked 46 of them by hand, on the soft-grey panels of the home and Managed Services pages, and they meet the standard. The other 257 have not been individually verified. We would rather tell you that than fold them into a total and call it measured.
• The chat assistant has been checked for keyboard reachability but not for the full screen reader experience, including how new messages are announced.
• We have not tested with magnification above 200 percent, or with voice control software.

If something blocks you

Email support@firstcoast.ai and tell us what you were trying to do and what got in the way. A person reads it. We aim to reply within two business days, and if we cannot fix it quickly we will find another way to get you what you needed.

This also applies to anything we have built for you. Accessibility problems in client work are treated as defects, not enhancements.

Last full review 7 August 2026, against build e0b99cd of the codebase this site was promoted from. The site has since moved to its own repository and gained eight case-study pages built from the same components; a fresh full review is planned, and this line will be re-stamped when it lands.