Accessibility

What we aim for

• Keyboard access

  Primary flows — navigation, forms, sample-case interactions, and funnel steps — are designed to be operable without a mouse, with visible focus states.

• Readable structure

  Pages use semantic headings, labeled form fields, and sufficient contrast on body text and interactive controls. Decorative diagrams include titles and descriptions for assistive tech.

• Secure routes stay usable

  Authenticated upload and results pages follow the same accessibility targets as marketing pages. We do not trade usability for security theater.

Ongoing work

Accessibility is continuous, not a one-time checklist. As we ship new reports, diagrams, and funnel steps, we re-test keyboard paths, labels, and contrast. If a page falls short, tell us — we treat accessibility bugs like product bugs.

Known areas we actively improve: complex SVG diagrams on smaller screens, dense chronology tables in the sample case, and focus order after dynamic form states in the evaluation funnel.

Report a barrier

If you encounter a missing label, focus trap, insufficient contrast, or anything that blocks use, please report it. Include the page URL, what you were trying to do, and the assistive technology or browser you were using if you know it.

Please do not include PHI in accessibility reports. Use /contact or email contact@everycase.ai.