Skip to main content

Accessibility Statement

Last updated: 8 August 2026

Realvue is a visual product: it turns an audience count into a crowd of illustrated people. That makes accessibility harder and more important, not less. This page says plainly what we have done, what we know is still wrong, and how to tell us when we have missed something.

Realvue is operated by 7VN Intelligence LLC, a company registered in Wyoming, United States.

The standard we are working to

We target WCAG 2.2 Level AA. Where this statement says something passes, it means it was measured with automated tooling (axe-core and Lighthouse in Chrome) or checked by hand in a browser, not that it was assumed from the code.

We are not yet claiming full conformance. Realvue is partially conformant with WCAG 2.2 Level AA: most of the public product meets it, and the exceptions are listed below.

What is in place

  • Keyboard access.Every control on the public pages can be reached and operated with a keyboard, and a “Skip to main content” link is the first thing you reach on every page so you do not have to tab through the navigation each time.
  • A visible focus indicator.Whatever you are on is outlined clearly, including in places where the design previously replaced the browser's own outline with a faint border.
  • Text contrast. Body text, buttons and the brand gradient all meet the WCAG 2.2 AA contrast thresholds. The gradient on the main call-to-action and on the large headline numbers was deepened specifically so white and coloured text on it is legible.
  • Reduced motion is respected. If your device asks for reduced motion, the animated crowds stop moving. They still appear, fully populated, and they still update when the real numbers change; they simply hold still instead of animating continuously.
  • Labels and structure. Form fields have real labels even where the design shows none on screen, headings run in order, page content sits inside proper landmarks, and controls whose state was previously shown only by colour now announce that state.
  • Touch targets. Interactive elements on the public pages are at least 24 by 24 CSS pixels, which is the WCAG 2.2 AA requirement, and in practice most are considerably larger.
  • Decorative visuals are marked as decorative. The crowd canvases are hidden from screen readers, because the number they illustrate is always written out in text beside them.

Known gaps

These are real and we would rather you heard them from us. Target dates are our honest intent, not a contractual commitment.

  • The crowd itself has no non-visual equivalent beyond the number. A screen-reader user gets the audience total and the platform breakdown as text, but not the arrangement, the location view, or the sense of scale that the picture carries. We consider a richer text summary the correct fix rather than describing individual figures. Target: Q4 2026.
  • The signed-in dashboard has not had the same audit. This pass covered the public surfaces: the landing page, sign-in, public creator profiles, shared live links, and these legal pages. The dashboard, settings and analytics screens are next. Target: Q4 2026.
  • Some page regions on the shared live-crowd view still sit outside a landmark. That view is shared with the signed-in product and is being reworked; the landmark structure will be finished with it. Target: Q4 2026.
  • No formal testing with assistive technology users. Our checks so far are automated tooling plus manual keyboard and screen-reader passes by the team. We have not run a session with people who use these tools daily, which is the only way to find the problems tooling cannot see. Target: before general availability.
  • Third-party content. The checkout is hosted by Lemon Squeezy and the map tiles come from CARTO. We do not control their accessibility, and we have not audited them.
  • English only. The interface is currently available in English only, which is a barrier in itself for some users.

Tell us when we get it wrong

If any part of Realvue is difficult or impossible for you to use, we want to hear about it, and we will help you get to what you needed in the meantime. There is no wrong way to report it.

  • Email. info@realvue.to. This is a monitored inbox and the fastest route.
  • Inside the product. Signed-in users can open Report a bug from the account menu. Say it is an accessibility problem and it is treated as a priority.
  • By post. Ask by email and we will give you the postal address for 7VN Intelligence LLC in Wyoming, United States.

We aim to acknowledge accessibility reports within 5 working days and to tell you what we are going to do about it, and when, within 10.

If we do not resolve it

If our response does not resolve your problem, you can escalate. In the European Union, the European Accessibility Act is enforced by the market surveillance authority of your member state. In the United States, complaints under the Americans with Disabilities Act can be filed with the Department of Justice Civil Rights Division. In the United Kingdom, the Equality Advisory and Support Service can advise.

How this statement was prepared

Self-assessed. The public pages were tested in Chrome with axe-core and Lighthouse, with contrast ratios computed directly from the rendered colour values, plus manual keyboard and reduced-motion checks. It was last reviewed on the date shown at the top of this page, and it is reviewed again whenever a public surface changes materially.

See also our Privacy Policy and Terms of Service.