Accessibility Statement

We aim to make Caseflow and Family Portal usable by people with disabilities, including people using keyboards, screen readers, zoom, high contrast, voice input, and other assistive technology. Accessibility is part of product quality and ongoing maintenance.

Our target is WCAG 2.2 Level AA for public websites, authentication, checkout, account management, and core workspace journeys. Consumer e-commerce functions are also designed with the European Accessibility Act and Germany’s Accessibility Strengthening Act in mind. This statement is not a certification of complete conformance.

• Semantic headings, labels, landmarks, and keyboard-operable controls across maintained flows.
• Visible focus states, responsive layouts, text-size controls, and color contrast considered in the design system.
• Alternative text and accessible names for maintained product imagery and controls.
• Status and error messages designed to remain understandable without color alone.
• Language and locale controls, reduced-motion-compatible browser behavior, and support for browser zoom.

Complex family-tree canvases, generated PDFs, third-party payment or OAuth pages, user-uploaded documents, rich document editing, scanned images, maps, charts, and legacy components may not provide an equivalent experience in every assistive technology. Third-party or user-generated content may be outside our control. We prioritize account access, checkout, legal information, and core record workflows when remediating barriers.

If you encounter a barrier or need information in an accessible format, contact support and include the page, task, browser, assistive technology, and preferred format. Do not include sensitive case content unless necessary. We will acknowledge the request, assess an accessible alternative, and prioritize remediation based on severity and impact.

Caseflow public contact: Atul Goel · Wittenkamp 24, 22307 Hamburg, Germany · +49-15560061837 · info@caseflow.my.

This statement is reviewed when material interfaces change and at least annually. Conformance claims should be supported by current automated and manual testing before publication.