Accessibility Statement
Last updated: 10/1/2026
1. Our commitment
ToolBX Media builds websites for healthcare, telehealth, and commerce brands. The people who use those sites are often unwell, in a hurry, or on an old phone with a cracked screen. We hold this site to the standard we build client sites to. If any part of it is hard for you to use, we want to know, and we will fix it.
2. Conformance status
This site is built to the Web Content Accessibility Guidelines version 2.2, Level AA, published by the World Wide Web Consortium. Testing across every page has not found an outstanding Level A or Level AA failure. We do not claim more than that: some success criteria cannot be settled by testing alone, and those are set out under Known limitations below.
3. How this site was evaluated
Three passes, run against every page of the site rather than a representative sample. Colour contrast was measured on every text node, with the full background stack flattened first, the way a browser actually paints it. A rule engine covering 94 separate WCAG checks was run on every page. Keyboard behaviour was then exercised by hand: the skip link, tab order, focus visibility, the mobile menu, and the project quiz from the first field through to submission. Testing was carried out in October 2026 using Chrome on macOS, at desktop width and at 320 pixels wide.
4. What that means in practice
Every piece of text on the site meets the AA contrast threshold against the background it actually sits on. Every field in the project quiz has a label that stays visible to assistive technology after you start typing, rather than a placeholder that disappears. Each page has one main landmark and a skip link that moves focus to it. Keyboard focus is always visible, and the sticky header never covers the element you have just moved to. The site reflows to 320 pixels wide without a horizontal scrollbar. No instruction anywhere depends on colour alone.
5. Known limitations
Third party components. The chat assistant is supplied by Voiceflow and the scheduling window by Calendly. Both render inside this site, and we control neither their markup nor their behaviour. We have not audited either. If one of them stands between you and what you came for, email or call us and we will handle it that way instead. Testing with assistive technology. This site has been tested by automated tools and by keyboard. It has not yet been tested by people who use a screen reader, a screen magnifier, or voice control as their everyday means of access. That testing finds problems no tool finds, and we have not done it. We would rather say so than imply a coverage we do not have.
6. Report a barrier
Email ask@toolbxmedia.com or call 949 414 6870. Tell us the page, what you were trying to do, and what got in the way. You do not need to know the technical name for it. We aim to respond within five business days.
7. Standards and the law
WCAG 2.2 Level AA is the benchmark this site is built to. The Americans with Disabilities Act does not itself set out a technical standard for private commercial websites. In April 2024 the Department of Justice adopted WCAG 2.1 Level AA as the requirement for state and local government websites under Title II of the Act. WCAG 2.2 is the current version of that same standard.
8. Technical specifications
This site relies on HTML, CSS, and JavaScript. Pages are generated as static HTML, so the content is present in the markup before any script runs, and the site remains readable if JavaScript fails to load.
Answer a few questions. We’ll find the cleanest path to launch or scale.
A stepped project quiz gets better answers than a blank contact form. Tell us what you are building, where the friction is, and what needs to happen next.
Not every project needs the same build path.
Some brands need a clean launch. Some need a conversion rebuild. Some need intake, checkout, tracking, and follow-up fixed before scaling ads. The quiz helps separate the real need from the surface request.
Map the build before we talk.
Five quick steps. No giant table form. Your answers get packaged into one project inquiry so we can reply with a clearer next step.