Our Conformance Target
We target the Web Content Accessibility Guidelines version 2.1 at Level AA for the marketing site, the sign-in flow, the attendee portal and the customer portal. Target means the standard we build and test against, and we are partially conformant: most of the product meets it and the known exceptions are listed below.
We have not commissioned an independent accessibility audit and hold no VPAT or Accessibility Conformance Report. If your organization requires one before purchase, tell us and we will say plainly whether we can meet the requirement.
What Is In Place
Every form control carries a visible label, not just a placeholder, because a placeholder disappears the moment somebody types and takes the question with it. Icon-only buttons carry an accessible name.
Every interactive element has a visible keyboard focus state that differs from its resting state, so somebody navigating by keyboard can always see where they are. Nothing is reachable by pointer alone.
Text meets a 4.5 to 1 contrast ratio against its background, including under the pointer: a hover state may change color but never readability, and that is measured rather than assumed.
Pages are built from real headings in order, landmarks, and tables with proper header cells, so a screen reader gets a structure rather than a wall of text. Zoom is never disabled and the viewport is never locked, so text can be enlarged to 200 percent without loss of content.
Tap targets are at least 44 pixels, text never drops below 12 pixels, tables stack into labeled lists on a phone rather than scrolling sideways, and no page scrolls horizontally at any width. Color is never the only way information is conveyed: a status is a shape and a word as well as a color.
Known Limitations
A few data-dense admin tables are wide, and while they stack on a narrow screen rather than scrolling sideways, the stacked form is long. We would rather give you every column than hide one.
Charts in the reporting screens convey their point through shape and an accompanying figure, but a complex chart is still easier to read visually than through a screen reader. The underlying numbers are available as a table or an export in every case.
Some third-party components we embed, notably the payment fields hosted by Stripe and the reCAPTCHA widget, are outside our control. We have no ability to change their markup and rely on their vendors' own conformance.
Content written by a customer, such as an email template or an event description, is as accessible as the person who wrote it made it. We cannot fix a missing image description in somebody else's copy, though the editor does prompt for one.
Telling Us About A Problem
If something on this site or in the product is in your way, write to dev@opvii.local and say what you were trying to do, the page you were on, and what happened. You do not need to know the standard or name the guideline.
We aim to acknowledge within two business days and to tell you either when it will be fixed or what the alternative is in the meantime. An accessibility report is treated as a defect report, not as a feature request.
If You Cannot Use Part Of The Product
Registration, reminders and attendance can all be handled on your behalf. Write to dev@opvii.local or call the number in the site header, and a person will complete the task with you rather than pointing you back at the screen that did not work.