Accessibility

Accessibility Statement

Preflix AI's accessibility commitment for readable content, keyboard support, semantic structure, contrast, and accommodation requests.

  • Keyboard support
  • Visible focus
  • Accommodation contact
Person using a laptop with large readable interface elements

Commitment

Preflix AI is intended for people navigating stressful medical bills, so accessibility is not optional polish. The site should be readable, keyboard accessible, responsive, and understandable for users with different vision, mobility, cognitive, and assistive technology needs.

The design goal is WCAG-aligned usability with clear focus states, semantic headings, descriptive link text, meaningful alt text, visible labels, and content that remains usable on mobile and at increased zoom.

Accessibility Features

The current site includes a skip link, semantic landmarks, labeled forms, keyboard-friendly links and details panels, visible focus styles, reduced-motion handling, high contrast text, and responsive layouts that avoid horizontal scrolling.

Images include descriptive alt text when they add meaning. Decorative icons are hidden from assistive technology so screen reader output stays focused.

Ongoing Work

Accessibility is an ongoing process. Product surfaces should test upload workflows, report tables, document views, generated letters, dashboards, and account settings with keyboard navigation and screen readers.

The team should review pages before major releases, especially when adding forms, modals, charts, tables, or generated content.

Contact For Accommodations

If a visitor encounters an accessibility barrier, they should contact Preflix AI through the contact page and describe the page, the assistive technology or browser used, and the task they were trying to complete.

Support should offer an alternate way to access the information or complete the request while the underlying issue is reviewed.

Clear Boundaries

What This Means In Practice

These commitments keep the public website useful while leaving sensitive, account-specific work to protected workflows.

Keyboard First

Navigation, links, forms, details panels, and controls should be reachable without a mouse.

Readable By Default

The site uses high contrast, clear headings, large tap targets, and responsive text containers.

Feedback Channel

Accessibility requests and barriers should have a dedicated contact path.

FAQ

Common Questions

Short answers for the practical decisions this page is meant to support.

How can someone report an accessibility barrier?

Visitors should use the contact page, select Accessibility Help, and describe the page, browser, assistive technology, and task they were trying to complete.

Does the site support keyboard navigation?

The marketing site uses semantic links, forms, details panels, a skip link, and visible focus states so core pages can be navigated without a mouse.

What should ongoing testing include?

Product surfaces should test uploads, tables, report views, generated letters, dashboards, and settings with keyboard and screen reader workflows.

Accessibility Support

Tell Preflix AI About A Barrier So The Team Can Offer An Alternate Path