Acuity-Reliable LLC — Integrity. Experience. Results.

Accessibility

Conformance statement

We sell federal IT, where Section 508 is a contract clause rather than a preference. This page states what this site conforms to, how that was tested, and what has not been tested — because a claim you cannot check is worth nothing.

Conformance status

acuityreliable.com conforms to WCAG 2.1 Level AA. Section 508 of the Rehabilitation Act adopts WCAG 2.0 Level AA for web content, so this site meets the 508 standard and exceeds it.

The site was additionally tested against the success criteria added in WCAG 2.2 Level AA — including target size, focus appearance and focus not obscured — and meets those as well.

Standard
WCAG 2.1 Level AA, plus WCAG 2.2 Level AA criteria
Scope
All four pages of acuityreliable.com and the error page
Last evaluated
22 August 2026
Method
Automated rule checking, manual keyboard testing, accessibility-tree audit and code review
Evaluated by
Acuity-Reliable LLC (self-evaluation)

What was tested, and what was found

Automated tooling catches roughly a third of accessibility problems, so it was the starting point rather than the finish. Everything below was checked on the live site at 1440px and 390px.

  • Automated rules axe-core against WCAG 2.1 and 2.2 A and AA rule sets, on every page. Eleven contrast failures were found and fixed; the site now returns zero violations in every resting state. Text captured part-way through a cross-fade can be flagged by an automated tool while it is between opacities; that is a frame of an animation rather than how the text is presented, and it settles to full contrast.
  • Keyboard Every interactive element is reachable by Tab in a logical order, every focused element shows a visible indicator, and no element becomes trapped. The mobile navigation opens with the keyboard, reports its state, closes with Escape and returns focus to the button that opened it.
  • Focus not obscured The header is sticky, so scroll offsets are reserved for it. No focused element lands underneath the header on any page at either width.
  • Target size All controls meet the 24 by 24 pixel minimum, apart from links inline in a sentence, which the criterion exempts. Footer links measured 23.7 pixels and were corrected.
  • Reflow and zoom No horizontal scrolling at 320 pixels wide or at 200 percent zoom, on any page.
  • Structure One h1 per page, no skipped heading levels, a single main landmark, labelled navigation regions, a working skip link, and a declared page language.
  • Accessibility tree The structure a screen reader actually consumes was audited node by node on every page. Every element that requires an accessible name has one — zero unnamed controls, headings, regions or images across all five pages — and the order in which content is exposed matches the order it appears on screen.
  • Images and diagrams Every image carries alternative text. Decorative icons are hidden from assistive technology. The shared-services diagram hides its layout and states both halves of its argument in prose in the caption, so someone who cannot see it gets the whole point rather than a list of disconnected labels.
  • Motion Everything that moves stops for prefers-reduced-motion. No animation loops indefinitely, and the diagram is shown already resolved rather than frozen part-way.
  • Forms Every control has a visible label. Missing required fields are announced through a live region, marked with aria-invalid, and focus moves to the first one.
  • Colour Colour is never the only way information is conveyed, and text meets contrast at AA on both the light and dark grounds used on the site.

What has not been tested

This is a self-evaluation. It has not been audited by an independent third party, and there is no VPAT for this site.

More importantly: the site has not been used by a person with a screen reader. We audited the accessibility tree node by node, which proves that every control has a name, a role and a state. What that cannot prove is whether the result is actually good to listen to — whether the reading order makes sense at speed, whether anything is verbose, repetitive or confusing in practice. Only someone working in JAWS, NVDA or VoiceOver can tell you that.

So the claim on this page is precise on purpose: the site meets the standard as written, and we have not yet had it used in anger by someone who depends on it. If that is you and something here does not work, we would far rather hear it than keep assuming.

Found a barrier?

Email marketing@acuityreliable.com and tell us what you were trying to do, which page, and what assistive technology you were using. We will reply within one business day and tell you what we can fix and when.