Critical flows are tested as complete journeys
Requester intake and confirmation, provider acknowledgement, onsite delivery, incident reporting, and organizer case handling must work by keyboard and screen reader, at zoom, in high contrast, and with reduced motion.
Accessible alternatives are part of the feature
Maps require equivalent lists, dependency graphs require ordered text, charts require data tables, QR codes require readable references, and generated PDFs require tagged structure and reading order.
Public pages follow the same standard
The marketing site and free tools use semantic landmarks, descriptive headings, visible focus, native controls, clear errors, large targets, responsive reflow, and motion that respects user preferences.
Keep decisions human and evidence explicit
Evencue records decisions made by authorized organizers and coordinates their event-specific consequences. It does not determine legal reasonableness, medical validity, entitlement, or venue certification. Provider and onsite views receive only the information required for their task.
What teams usually ask
Which standard does Evencue target?
WCAG 2.2 Level AA across public, requester, provider, onsite, and organizer workflows.
Are automated tests enough?
No. The release matrix also requires keyboard journeys, screen-reader smoke tests, zoom and reflow, forced-colors, reduced motion, touch-target, and accessible PDF checks.
Can users request an alternative format?
Requester and provider content should provide plain-language, accessible, and alternative-format paths appropriate to the event process.