Accessibility

Clover aims for clear typography, generous spacing, readable contrast, descriptive labels, predictable navigation, and calm visual states that reduce cognitive load.

The product should support users who are working quickly, multitasking, reviewing details, or returning to a provider launch after time away.

Accessibility review should apply to provider invites, forms, document uploads, payer readiness views, renewal reminders, tables, navigation, empty states, error messages, and account settings.

Clover should work with keyboard navigation where practical and should avoid relying on color alone to communicate status.

Clover is still evolving. Some early access features may not yet meet the accessibility standard Clover is working toward. As features mature, Clover should continue improving structure, labeling, focus states, screen reader support, and responsive behavior.

If you experience an accessibility barrier, contact Clover through the Contact page with the page, feature, device, browser, assistive technology if applicable, and a description of the issue.

Accessibility feedback helps Clover make provider launch work easier for more teams.