Built to be usable by everyone.

TMH Consulting, Inc. d/b/a Callback HQ is committed to ensuring digital accessibility for people with disabilities. We design and build Callback HQ to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, and to the applicable provisions of Title III of the Americans with Disabilities Act (ADA).

What we do

• Semantic HTML throughout — landmarks, headings, lists, buttons, and forms use the right elements so assistive technology can navigate them.
• Keyboard navigation for every interactive control. Tab order follows visual order; focus rings stay visible.
• Color contrast meets WCAG 2.2 AA (4.5:1 for body text, 3:1 for large text and UI components) on both light and dark surfaces.
• A “Skip to main content” link, consistent landmark regions, a single page heading, and a visible keyboard focus indicator on every interactive control.
• Form fields have associated labels and explicit error messaging; error states aren't communicated by color alone.
• Images, icons, and charts that convey meaning have text alternatives. Purely decorative imagery is marked aria-hidden.
• Auto-advancing content (countdowns, confirmations) can be dismissed or undone.
• Interactive targets are at least 24×24px (WCAG 2.2 SC 2.5.8), with most controls at 40px or larger. Layouts reflow without loss of content at 320px width and 200% zoom.
• Motion respects your prefers-reduced-motion setting; auto-advancing content (countdowns, confirmations) can be dismissed or undone.
• Tracking is opt-in: the consent banner and preferences dialog are fully keyboard operable, the dialog traps focus, closes on Escape, and returns focus to the control that opened it.

Where we know we have work to do

We test continuously but we're not perfect. Areas where we're actively improving:

• Inspection-report PDF rendering inside the claim review page is currently pre-formatted text — we're moving to an accessible structured view.
• Dashboard charts read out underlying data tables on screen readers, but we're adding richer summaries.
• Embedded intake widgets on third-party sites inherit the host page's accessibility baseline. We're working with embedders to ensure the host meets WCAG too.

Reporting an accessibility issue

If you encounter content or functionality that's not accessible to you, please tell us. We treat accessibility reports as high priority and will work with you to provide the same information another way while we fix the underlying issue.

Enforcement & formal complaints

If you're not satisfied with our response, you can file a complaint with the U.S. Department of Justice, Civil Rights Division, under the Americans with Disabilities Act: https://www.ada.gov/file-a-complaint/.

Conformance standard

This statement describes our commitment to WCAG 2.2 Level AA. It does not constitute a legal warranty. We update it whenever we make material changes to the product's accessibility. Last reviewed 2026-07-08.