Accessibility Statement
Effective August 25, 2026. Last updated August 25, 2026.
1. Our commitment
Top ABA Therapy is being built toward WCAG 2.2 Level AA across provider search, profiles, comparison, careers, resources, accounts, and these governance pages.
Accessibility is treated as a release gate rather than a decorative checklist applied after pages are built. If a core task cannot be completed without a pointer, that is a defect and it blocks the release.
2. Conformance status
We do not claim conformance. WCAG 2.2 AA is the target, and a claim will be made only when live browser and assistive-technology evidence supports it, not on the strength of an automated scan.
3. What the implementation targets
- Core tasks are server-rendered and completable by keyboard alone, with visible focus on every control.
- Layouts reflow at 320 CSS pixels and remain usable at 200% zoom without horizontal scrolling.
- Landmarks, heading order, labels, error associations, status announcements, current-page state, and native disclosure semantics are provided rather than simulated.
- Motion is decorative only. Reveal animations stand down under prefers-reduced-motion, and no content depends on an animation running to become readable.
- Colour is never the only carrier of meaning, and text contrast targets AA at its rendered size.
4. Known limitations
Stated rather than hidden, because a statement that lists nothing is not credible:
- Third-party embeds and external application destinations follow their own accessibility practices, which we do not control.
- Data tables carrying wide evidence sets scroll horizontally inside their own container on narrow viewports.
- Assistive-technology verification across the full 340-page directory surface is not complete; the governance and shell pages have had the most attention.
5. How we test
- Complete core tasks by keyboard: search, compare, open a profile, navigate careers, and use the governance routes without a pointer.
- Verify names, roles, states, and announcements with a screen reader: landmarks, heading order, labels, error associations, live status, disclosure state.
- Check reflow and zoom at 320 CSS pixels and 200%, confirming no content or function is lost.
- Confirm the rendered page in a real browser, not only in the build output. Static checks are necessary and they are not sufficient.
6. Report a barrier
Write to topabatherapy@gmail.com with the page URL, what you were trying to do, and what stopped you. If you are comfortable saying so, the browser and assistive technology you were using makes it much faster to reproduce.
Please do not include a diagnosis, treatment records, or an insurance member identifier. None of it helps us fix the barrier, and this is a public directory rather than a clinical system.
7. Response and remediation
We acknowledge a barrier report within five business days and tell you what we found, what we are going to do, and roughly when. Where a fix will take time we will say so and describe a way to complete the task in the meantime.
Barriers that prevent a core task being completed are treated as release-blocking rather than queued.