Contact Us
Accessibility Statement

Accessibility

We build accessible systems for public-sector clients, and hold this site to the same standard. Here is what we aim for, how we check it, and where we still fall short.

Our target

nexaces.com aims to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, the level the U.S. Department of Justice's 2024 ADA Title II rule sets for state and local government websites.

Current status: partially conforms. We have audited the site and fixed what we found, but the gaps listed below mean we cannot yet say every page fully meets the standard.

How we test

  • An automated scan with axe-core against the WCAG 2.0 and 2.1 A and AA rules, covering every page template at desktop and phone widths.
  • A keyboard-only pass: every link, menu, form and button reachable with Tab, usable with Enter or Space, with a visible focus outline and a “Skip to main content” link.
  • Colour contrast checked against the 4.5:1 minimum for body text and 3:1 for large text. The one exception is listed under known gaps below.
  • Page structure checked for a single main heading, labelled landmarks (header, main content, footer), and a text name on every icon-only link and button.

We repeat the automated scan when we change a page template, and review this statement at least once a year. It was last reviewed in October 2026.

Known gaps

  • White text on orange buttons. Our buttons and a few highlighted words use the brand orange, and white text on it falls short of the 4.5:1 contrast minimum. The labels are short and bold; if any are hard to read, tell us.
  • Google reCAPTCHA on the contact forms. The forms use Google's invisible reCAPTCHA, which runs when you press Submit and asks nothing of most visitors. Occasionally it shows Google's own image challenge, whose accessibility we do not control. It offers an audio option; if it still blocks you, email us instead and we will treat it as a form submission.
  • Capability statement PDF. The one-page capability statement has not yet been checked against PDF/UA. Everything in it is also on the Capabilities page as ordinary text, and we will send an accessible version on request.
  • Images in older blog posts and case studies. Some images added through our content system before this review may have alt text that describes the image less well than it should. We are working through them.
  • Screen-reader testing. We have tested with automated tools and by keyboard alone, but have not yet completed a full review with a screen reader such as NVDA, JAWS or VoiceOver. Problems you find this way are especially useful to us.

Tell us about a problem

If something on this site is hard to use, or you need any of it in another format, email info@nexaces.com with the page address and what went wrong. A person will reply within two business days, and tell you when it is fixed. You can also reach us through the contact page.