Overview
Proxi is committed to making the Guide experience accessible to participants of all abilities. This statement covers the public-facing pages participants interact with: the registration page and the main Guide page — including the Places list, My List, and location detail views.
Our target standard is WCAG 2.1 Level AA — the benchmark referenced in the Americans with Disabilities Act (ADA) web accessibility guidance and most state and local accessibility requirements.
The Guide shares its core page structure and interaction patterns with the Passport Challenge. Rather than repeat everything, this document focuses on what is unique to the Guide experience and notes where Passport documentation applies. For the interactive map linked from every Guide, see Proxi Interactive Map — Accessibility Statement.
What the Guide Experience Includes
The participant-facing experience consists of:
Registration page — email, name, and phone fields; terms acceptance; optional payment checkout; and a login/link flow for returning participants
Guide page — tabbed navigation across About, Places, My List, and Share sections
Location cards — name, address, description, images, and category for each place in the Guide
Save button — on each location card, lets participants add places to their personal My List
My List tab — a personal, saved collection of locations chosen by the participant
Location detail drawer — a modal overlay with full location information, images, and optional check-in prompt
Interactive map — a linked Google Maps-powered view of all locations. For full details on map accessibility, see Proxi Interactive Map — Accessibility Statement.
What We've Built for Accessibility
Shared Foundation with Passport
The Guide is built on the same challenge-page component as the Passport experience. The following accessibility features are identical and are documented fully in the Proxi Interactive Map — Accessibility Statement :
Tab navigation with full ARIA roles (tablist, tab, tabpanel), keyboard support (Arrow keys, Home/End, Enter/Space), and sub-tab keyboard support
Modal dialogs with role="dialog", aria-modal, Escape to close, and focus management
Error messages using role="alert" and aria-live
Registration form: native HTML inputs with proper label associations, aria-required on required fields, keyboard-navigable, compatible with browser autofill and assistive technology
Focus indicators on all interactive elements
Semantic HTML structure (header, nav, main, section, footer)
No images of text
Zoom enabled on mobile — no user-scalable restrictions
Page language set dynamically via the lang attribute when translation is active
"Skip to main content" link at the top of the page
Decorative icons marked with aria-hidden="true"
Location Cards and the Places List
Location cards in the Places tab and My List tab are keyboard focusable and screen reader compatible.
Each card has role="button", a tabindex, and an aria-label identifying the location by name — screen readers announce it clearly as an actionable element
Cards are activated with Enter or Space, opening the location detail drawer
Location images include descriptive alt text
Locations that have been checked in display a status icon with alt="Checked in" so screen reader users receive the same confirmation sighted participants see
The Save / My List Feature
The Save button on each location card is a native HTML button element — it is keyboard accessible and announced correctly by screen readers. Saving a location does not open the card or cause unexpected navigation. The button state updates between "Save" and "Saved" as participants add and remove locations from their list.
The My List tab uses the same accessible card pattern as the Places tab. Once a participant has saved locations, they can navigate, read, and interact with every saved place using keyboard alone.
A Simpler Experience by Design
The Guide does not include a leaderboard, points system, or progress bar. This reduces the number of dynamic, state-driven components participants interact with, which lowers the overall surface area for accessibility issues. There are no reward animations, no rank updates, and no completion meters — just a clean list of places and a personal saved collection.
Shared Responsibility: Color Contrast
WCAG 2.1 Level AA requires a 4.5:1 contrast ratio between text and its background for body text, and 3:1 for large text and UI components.
Because Guide experiences are branded by your organization, the colors participants see depend on choices made during setup. The admin color picker displays a live contrast warning when selected brand colors do not meet the 4.5:1 threshold.
We guide — your team makes the final call. If your organization needs to demonstrate compliance, review your Guide colors using a free tool like the WebAIM Contrast Checker after setup.
The Interactive Map
Every Guide links to a Proxi interactive map where participants can see all locations spatially, filter by category, and check in. The map experience has its own accessibility features and its own admin configuration guidance that affects accessibility.
For full details, see:
The key point for Guide participants: the Browse Locations panel on the map provides a complete text-based list of every location — participants can browse and read all location information without interacting with the map canvas.
Known Limitations
We believe in being straightforward about areas where accessibility depends on participant hardware or capabilities.
Admin portal
This statement covers the participant-facing experience only. Accessibility improvements to the Proxi admin portal are ongoing and will be documented separately
Map canvas keyboard limitations
These are documented in the Interactive Map accessibility statement. The Browse Locations text list is the designed accessible path for keyboard and screen reader users.
What We're Working On
Accessibility is an ongoing commitment, not a one-time checklist. Here is where we are actively investing:
Expanding accessibility coverage across the admin portal
Evaluating automated accessibility testing as part of our development and release process
Continuing to audit participant-facing flows as we add new features
Feedback and Accommodation Requests
If you or a participant encounters a barrier in the Guide experience, we want to hear about it.
Contact Proxi support through the chat widget in your Proxi dashboard, or reach out to your account contact directly.
Organizers who need to support specific accessibility accommodations for their event or district are encouraged to reach out — we can help you understand your options and plan accordingly.
Technical Reference
Standard | Target Level |
WCAG | 2.1 Level AA |
Keyboard operability | WCAG 2.1 Success Criteria 2.1.1, 2.1.2 |
Focus visible | WCAG 2.1 Success Criterion 2.4.7 |
Name, Role, Value (ARIA) | WCAG 2.1 Success Criterion 4.1.2 |
Status messages | WCAG 2.1 Success Criterion 4.1.3 |
Contrast (minimum) | WCAG 2.1 Success Criterion 1.4.3 |
Language of page | WCAG 2.1 Success Criterion 3.1.1 |
Images of text | WCAG 2.1 Success Criterion 1.4.5 |
Last updated: March 2026. This statement will be reviewed and updated as the Guide experience evolves.
A note on using this document with city officials or legal reviewers: This statement is intended to describe Proxi's current implementation honestly. It is not a legal certification. Organizations with specific ADA compliance requirements should consult with an accessibility specialist to assess their full program — including any communications, printed materials, and in-person components that fall outside the Proxi platform.