Skip to main content

Proxi Passport Challenge — Accessibility Statement

Proxi is committed to making the Passport Challenge experience accessible to participants of all abilities. This statement covers the public-facing pages that participants interact with.

Written by Melinda Haughey
Updated today

Overview

Proxi is committed to making the Passport Challenge experience accessible to participants of all abilities. This statement covers the public-facing pages that participants interact with: the registration page, the main challenge page, and all check-in and reward flows.

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.

This statement describes what we have built, where shared responsibility exists between Proxi and your organization, and where we are continuing to improve.


What the Passport 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

  • Challenge page — tabbed navigation across About, Locations, Activities, Progress, Leaderboard, Photo Feed, and Share sections

  • Check-in flows — QR code scanning, geolocation confirmation, and optional photo submission

  • Reward tracking — badges, progress bars, and leaderboard rankings

  • Location detail drawers — modal overlays with location descriptions, images, and check-in prompts

  • Interactive map — a Google Maps-powered map view where participants can see locations, check in, and explore. For full details on map accessibility, see Proxi Interactive Map — Accessibility Statement


What We've Built for Accessibility

Keyboard Navigation

Every interactive element in the Passport experience is operable by keyboard alone — no mouse required.

  • Tab navigation uses standard keyboard controls: Arrow keys to move between tabs, Home/End to jump to the first or last tab, and Enter or Space to activate

  • All buttons use native HTML button elements, which are keyboard-focusable and screen reader compatible by default

  • Modal dialogs (location drawers, check-in prompts) support Escape to close, move focus inside on open, and return focus to the triggering element on close

  • A "Skip to main content" link is available at the top of the page for keyboard users who want to bypass navigation

Screen Reader Compatibility

The experience is built with semantic HTML and ARIA attributes to support screen readers such as JAWS, NVDA, and VoiceOver.

  • Tab navigation uses ARIA roles (tablist, tab, tabpanel) with appropriate aria-selected and aria-label attributes

  • Modal dialogs include role="dialog" and aria-modal so screen readers correctly identify them as overlays

  • Error messages and form validation feedback use role="alert" and aria-live — screen readers announce these automatically without requiring focus to move

  • Progress bars include role="progressbar" with aria-valuenow, aria-valuemax, and a descriptive label so screen readers can communicate completion percentage

  • Required form fields are marked with aria-required

  • Images include descriptive alt text — challenge names, logos, reward icons, and location images all have meaningful descriptions

  • Page language is set dynamically via the lang attribute when translations are active

Forms

The registration form uses native HTML input elements with proper label associations. Fields are clearly labeled, keyboard navigable, and compatible with browser autofill and assistive technology.

Visual Design

  • Focus indicators are visible on all interactive elements during keyboard navigation

  • All text is rendered as HTML — no images of text

  • The page uses semantic structure: header, nav, main, section, and footer elements

Interactions

  • No complex gestures (swipes, multi-finger taps, or drag-and-drop) are required to complete any participant action

  • All core interactions are single-click or single-tap


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.

Proxi supports this standard through guidance built into the platform:

  • The admin color picker displays a live contrast warning when your selected brand colors do not meet the 4.5:1 threshold

  • We recommend testing your chosen colors before publishing your challenge

Because Passport experiences are branded by your organization, the colors participants see depend on the choices made during setup. We guide — your team makes the final call. If your organization needs to demonstrate compliance, we recommend reviewing your challenge colors using a free tool like the WebAIM Contrast Checker after setup.


The Interactive Map

Every Passport Challenge is linked to a Proxi interactive map where participants can see locations, get directions, and check in. The map experience has its own accessibility features — including a full searchable text list of locations, keyboard-accessible filters, and screen reader support.

Because the interactive map is a shared component across all Proxi experiences, we document its accessibility separately. For full details — including admin configuration guidance that affects accessibility — see:

Key highlights relevant to Passport participants:

  • The Browse Locations panel provides a complete text-based list of every location in the challenge — participants can browse, search, and read location details without interacting with the map canvas

  • On mobile, tapping a location in the list shows full details inline with a "Back to list" button — participants stay in the list context

  • For scavenger hunts, the list view respects clue cards — hidden location details are not revealed

  • The "View on Map" button lets participants jump to the spatial view when they choose to


Known Limitations

We believe in being straightforward about areas where accessibility depends on participant hardware or capabilities.

QR code check-in and geolocation

Some check-in methods require camera access (for QR scanning) or GPS access (for location confirmation). These features rely on device hardware and operating system permissions. Participants using certain assistive technologies or devices without camera or GPS access may find these flows challenging. We recommend that organizers consider whether alternate check-in methods (like check-in-codes or geolocation) are appropriate for their event.

Photo upload for activities

Some challenge activities require a photo submission. This requires access to a camera or photo library and may pose a barrier for some participants. Organizers can choose which activities require photos and may wish to offer alternatives for participants who need them.

Admin portal

This statement covers the participant-facing experience only. Accessibility improvements to the Proxi admin portal are ongoing and will be documented separately.


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 Passport 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 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 Passport 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.

Did this answer your question?