Accessibility
How this site is built, and where it falls short
We build this site to WCAG 2.2 Level AA. This page names that target, the limitations we already know about, and the way we test.
Last reviewed
TrueStep HR builds this site to the Web Content Accessibility Guidelines, version 2.2, Level AA. Courts and buyers use that benchmark, and our design system follows it deliberately.
We do not claim that the site fully conforms to the standard. Parts of it meet the standard, parts still need repair, and the list below separates the two honestly.
We treat accessibility as part of the design rather than a retrofit applied afterward. Every page comes out of a template that already carries visible focus, keyboard operation, generous target sizes, text that reflows on a narrow screen, and forms with genuine labels.
That decision matters more here than it would elsewhere. A business selling work built to a published standard has to be operable by the practitioners who buy that work.
Known limitations
- Some documents in the catalog are PDFs with incomplete tagging, so a screen reader may announce their contents out of order. Tell us which document you need and we will send an accessible version.
- Checkout runs on Shopify. We test the path into it and we control the pages around it, and the checkout code itself is not ours to repair.
- We are retesting the calculators and assessments for keyboard order, and for results a screen reader can announce properly. Several have not been through that pass yet.
- Older reference notes predate our current heading and contrast rules, and we are reworking them one note at a time.
- The downloaded Word, Excel, and PDF documents vary in quality. We are rebuilding them with proper heading structure and table headers, and that work is unfinished.
- Another company serves any embedded scheduler or payment window, so the accessibility of those components belongs to them rather than to us.
How this is tested
- Automated testing catches roughly a third of the problems that actually matter, so it is where our testing starts rather than where it stops.
- We drive every template with the keyboard alone, including each modal, filter, form, and calculator on the page.
- We read pages with a screen reader, NVDA on Windows and VoiceOver on Mac, to hear what the page genuinely announces.
- We check color contrast, focus visibility, target size, text at double zoom, and reflow at the narrowest common phone width.
- A new template goes through the same pass before it ships, which is why these checks live inside the build rather than inside an annual audit.
Why there is no accessibility widget here
We decided against an accessibility overlay, and the decision belongs on the record rather than in somebody's head. In April 2025 the Federal Trade Commission entered a final order against an overlay vendor over the claim that its product made any site conform. Plaintiffs still sue overlaid sites in volume, because the pages underneath the widget remain broken. Buying a badge instead of repairing the page would be exactly the wrong trade for this business, so the repairs go into the templates.
Tell us about a barrier
Email support@truestephr.com with the page address and a description of what happened. Name your browser and any assistive technology you use, if you can. You get a reply within one business day, and either a repair or a workaround with a date attached to it.
This statement was last reviewed on .