1. Commitment
Events are for everyone, so the pages guests touch must be usable by everyone. Everlage designs customer-facing surfaces — event pages, checkout, tickets and emails — to align with WCAG 2.1 AA principles.
2. What that means in practice
Semantic structure and landmarks, full keyboard operability of registration and checkout, visible focus states, form labels and error messages readable by screen readers, and color contrast of at least 4.5:1 for text. Tenant theme overrides are validated: the platform refuses color combinations that fail contrast.
3. Right-to-left and language support
Storefronts render fully right-to-left for Hebrew and support English and Russian, including dates, numerals and form validation messages.
4. The operator console
The console is keyboard-navigable and screen-reader labeled on core flows (event creation, orders, check-in monitoring). We audit new modules against the same checklist before release.
5. Known limitations
Some advanced visualizations (seat maps, live charts) have text-based equivalents in reports rather than fully non-visual interaction. This is on the accessibility backlog.
6. Feedback
If you or a guest hits an accessibility barrier, email contact@everlage.com with the page and assistive technology used. Accessibility reports are triaged with priority-support severity regardless of plan.
