Accessibility Statement

How we build vorafinancial.io and the Vora app to be usable by everyone, what we know still falls short, and how to reach us.

Last updated November 4, 2026

Draft for counsel review

In short

We aim to meet WCAG 2.2 Level AA on vorafinancial.io and in the Vora app.
We check every app page with automated accessibility tests and reviewed every screen by hand in October 2026.
Some parts still fall short, mainly data-dense tables and charts and the muted product videos on the website. We list them below.
If something gets in your way, email info@vorafinancial.io or call 786-654-1233. We aim to respond within 5 business days.

This summary is for convenience. The full text below governs.

1. Our commitment

Vora Financial LLC ("Vora", "we", "us") wants everyone to be able to use our website and our software, including people who use a screen reader, magnification, voice control, a keyboard instead of a mouse, or settings that reduce motion. Our customers are insurance agencies, and their agents, staff and clients rely on the Vora app every day. An accessibility problem for any of them is a problem we want to fix.

Accessibility is part of how we design and test, not a separate project. This statement explains the standard we work to, what we do to meet it, where we know we fall short today, and how to tell us about a barrier.

2. What this statement covers

The website at vorafinancial.io, including product pages, guides, the interactive demo, forms and our legal pages.
The Vora app at https://app.vorafinancial.io, on desktop and mobile web, including the agent and admin workspace, the softphone and power dialer screens, messaging, and the client portal that agencies offer to their clients.

Some content is outside our control. This includes documents, recordings and images that agencies upload, carrier websites and forms we link to, and third-party services such as payment checkout pages. We still want to hear about barriers there, and we will help where we can.

3. The standard we work to

We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, published by the World Wide Web Consortium (W3C). WCAG explains how to make web content perceivable, operable, understandable and robust for people with disabilities.

Conformance status: partially conformant. This means most of the website and app meet the standard, but some parts do not yet fully conform. Section 5 lists the parts we know about.

4. What we do

Design system

Every color comes from shared design tokens. Text has a contrast ratio of at least 4.5:1 against its background (3:1 for large text and for the edges of controls), in both light and dark themes.
Color is never the only signal. Every status pairs a color with a text label and a shape, so it reads for people with color-vision differences.
Touch targets are at least 44 pixels on touch screens. Pages work at 390 pixels wide without scrolling sideways, and wide tables turn into record cards on small screens.
Copy uses plain language, and dates include the year where it could be unclear.

Keyboard and focus

Everything in the app can be reached and used with a keyboard, with a visible focus ring on the element you are on.
Pages use labelled landmarks and headings, and the website has a "Skip to main content" link.
Form fields have visible labels, and errors are announced and linked to the field they belong to.

Motion

We honor your device's reduced-motion setting. With it on, reveal and scroll animations switch off and state changes still read clearly.
Background and product videos on the website are muted, pause when they scroll out of view, and do not play at all with reduced motion or a data-saver setting. A still image is shown instead.

Testing

Automated checks. Our end-to-end tests run the open-source axe accessibility engine against every page of the app that each role can reach, at desktop and phone widths, in light and dark themes, testing the WCAG 2.0, 2.1 and 2.2 Level A and AA rules. A new page that is not covered fails the build. The website's source code is checked with accessibility lint rules.
Audit. In October 2026 we reviewed every screen of the app by hand against our design rules and an accessibility checklist, alongside a full automated sweep. The sweep found no violations. The review found layout and consistency issues, which we fixed or scheduled.
Manual review. New screens are reviewed for keyboard use, focus order, labels and contrast before release.

5. Known limitations

Automated tools find only part of the issues people meet. These are the limitations we know about today and what we plan to do about each one.

Area	Limitation	What we are doing
Data-dense tables and charts (app)	Wide tables, commission breakdowns, analytics charts and the team hierarchy graph carry a lot of information at once. They can be slow to navigate with a screen reader or at high zoom, and some charts do not yet offer the same data as a table.	Adding a table or text view to each chart, and improving the hierarchy graph's starting view and controls.
Product videos (website)	The website's videos have no sound, so they need no captions. The product tour video has only a short text label, not a full text description of what it shows. Videos that loop while on screen have no pause button. They stop when they scroll out of view or when reduced motion is on.	Adding a pause control to looping videos and a text description of the product tour.
Animated previews (website)	Some product previews and the interactive demo animate to show how a feature works. With reduced motion off, this can be distracting.	Reduced motion switches these off. We are adding pause controls where an animation runs on its own.
Phone screens (app)	A few forms keep their desktop width on phones, and one settings tab row does not scroll the selected tab into view.	Scheduled fixes from the October 2026 audit.
Calls and audio (app)	Calls are audio by nature. Recordings have no transcript unless the agency turns on transcription. Audio files an agency uploads, such as voicemail messages and greetings, have no captions in the app.	Transcripts are shown with the recording when the agency enables transcription.
Uploaded and third-party content	Documents, images and reports that agencies upload, carrier forms and payment checkout pages may not meet WCAG.	We cannot change this content, but we will help you get the information another way.
Assistive technology testing	We have not yet completed structured testing with screen readers or other assistive technologies, or an independent third-party audit.	Planned. We will update this statement when it is done.

6. Compatibility

The website and app are built with standard, semantic HTML and use ARIA attributes only where native HTML is not enough, so they work with assistive technologies that follow web standards.

They are designed for the current and previous major versions of Chrome, Edge, Firefox and Safari on desktop, and Safari and Chrome on iOS and Android. The app needs JavaScript. Older browsers may display content incorrectly or miss features.

7. Feedback and help

If you have trouble using any part of our website or app, or you need information in a different way, please tell us. Feedback helps us find problems our tests miss.

Email: info@vorafinancial.io with "Accessibility" in the subject line. [DECISION: create a dedicated accessibility@ alias that routes to the same inbox, and point this link at it.]
Phone: 786-654-1233, Monday to Friday, during Eastern Time business hours.
Mail: Vora Financial LLC, 400 Sunny Isles Blvd, Sunny Isles Beach, FL 33160.

It helps to tell us the page or screen, what you were trying to do, what went wrong, and the browser and any assistive technology you use. You do not need to give a technical description.

Response target. We aim to respond within 5 business days. If a fix will take longer, we will tell you when to expect it and help you complete your task another way in the meantime.

Alternative formats

On request, we will provide our legal documents and other website content in an alternative format, such as accessible PDF, plain text or large print, or read it to you by phone. If you are a client of an agency that uses Vora, your agency is the best contact for your policy documents. We will help your agency provide them in a format that works for you.

8. Formal complaints

If you are not satisfied with our response, write to us at info@vorafinancial.io or at the mailing address above with the subject "Accessibility complaint". A member of our leadership team will review it and reply in writing within 10 business days, with what we will do and when.

You may also contact the U.S. Department of Justice, Civil Rights Division, at civilrights.justice.gov. Contacting us first is not required, but it is often the quickest way to resolve a problem.

9. How we assessed accessibility

We assessed the website and app ourselves. We did not use an outside auditor. Our assessment combined:

an automated axe sweep of every app page, role, screen width and color theme, which runs in every build;
a screen-by-screen review of the app in October 2026 against our design system and an accessibility checklist; and
manual keyboard, focus and contrast checks of the website.

This statement was prepared on November 4, 2026, based on that assessment. We review it at least once a year, and when we make a major change to the website or app.

Version 2026-11-04