Accessibility Statement

We target WCAG 2.1 Level AA conformance, with selected enhancements from WCAG 2.2 AA (such as enhanced target size and consistent help). We work toward full WCAG 2.2 AA conformance as we expand.

We follow the accessibility expectations of the Americans with Disabilities Act (ADA Title III) as applied to public-accommodation websites per the U.S. Department of Justice's web-accessibility guidance.

Keyboard navigation across every interactive surface.

Visible focus indicators on every interactive control.

Color contrast at WCAG AA levels (4.5:1 text; 3:1 UI).

Semantic HTML structure (headings, lists, landmarks).

Alt-text on images.

Programmatic labels on form controls.

Touch target sizes of at least 44×44 pixels on primary controls.

Mobile responsiveness at 320 CSS-pixel width.

Captions and transcripts on Anchor video content (when voice/avatar features are enabled by you).

Screen-reader-compatible chat surface with live-region announcements.

prefers-reduced-motion respect.

Acronyms (VA, BVA, HLR, etc.) defined on first use.

Plain-language copy calibrated for veteran audiences, including elderly users.

We also run automated accessibility checks (axe-core) on every code change and a manual checklist before each release.

Some legacy components may have keyboard or screen-reader gaps. We are actively improving.

PDF/DOCX exports are tagged for accessibility (PDF/UA target); some older templates may not fully conform.

Dictation-based input is not supported at launch; we use server-side speech-to-text only with strict BIPA-compliance review (currently out of scope).

If you experience an accessibility barrier on ClaimAnchor, please reach out:

Email: support@getclaimanchor.com with subject "Accessibility."

Describe the issue (what page, what device, what assistive technology if any, what you expected).

We aim to respond within 5 business days.

If we can't resolve in our application, we will work with you to find a way to accomplish what you need (e.g., a support person walks you through, or we send the result in an alternate format).

Documents (Privacy Policy, ToS, AI Disclosure, etc.) are available in HTML by default; we can provide a plain-text version on request.

ClaimAnchor is designed mobile-first and works on:

Modern desktop browsers (Chrome, Firefox, Safari, Edge).

iOS and Android mobile browsers.

Common screen readers (VoiceOver, NVDA, JAWS) and screen-magnification tools.

Voice-input tools on the operating-system level (Dragon, etc.).

If you use less common assistive technology and ClaimAnchor doesn't work as expected, please email us — we will troubleshoot together.

Accessibility is not a one-time check. We test with each release, run axe-core in CI, and prioritize accessibility-tagged issues. If you can help by reporting gaps or testing with us, please reach out.

Accessibility questions: support@getclaimanchor.com.