ACCESSIBILITY

PurposePass Accessibility Statement

PurposePass treats accessibility as an ongoing product-quality responsibility across public pages, ticketing and organizer workflows.

Reviewed August 30, 2026 · PurposePass portal

Our approach

PerceivableUse readable text, useful contrast and text alternatives for meaningful non-text content.

OperableSupport keyboard navigation, visible focus and controls that do not depend on hover alone.

UnderstandableKeep labels, instructions, validation and navigation consistent across public and organizer experiences.

RobustUse semantic HTML and accessible component patterns intended to work with modern browsers and assistive technologies.

1. Accessibility target

PurposePass uses WCAG 2.2 Level AA as its current design and evaluation target for web experiences where applicable. This is an improvement target, not an unconditional statement that every historical page, document, third-party integration or workflow has completed formal conformance testing.

2. Measures used in PurposePass

Semantic headings, landmarks, links, buttons, lists, tables and form controls.
Keyboard-accessible interactive functions and visible focus indicators.
Labels, required-field indicators, instructions and understandable validation feedback.
Responsive layouts intended to support zoom, text resizing and reflow.
Color/contrast choices that do not rely on color alone for essential meaning.
Reduced-motion support where motion is used.
Accessible dialog, status, error and notification patterns as components evolve.
Touch-target sizing and spacing appropriate for mobile ticketing and check-in workflows where practical.

3. Public site and organizer console

The public PurposePass site is intended to make events, pricing, product, support and legal information available using common navigation and input methods. Public event and organization pages use semantic headings, meaningful links, image alternative text and structured content so information remains understandable to people and compatible with assistive technology while also being machine-readable for legitimate discovery. Authenticated dashboards, financial tables, QR check-in tools and event-management interfaces can be denser and may require additional testing as features evolve.

4. Third-party services

PurposePass can link to independent payment providers, email services and other external tools. PurposePass does not control every accessibility characteristic of those services. Where PurposePass selects and embeds a third-party component, accessibility is considered as part of implementation and vendor review.

5. Evaluation and improvement

PurposePass may use code review, automated checks, keyboard testing, responsive testing, manual inspection and assistive-technology testing. Automated tools can identify some issues but do not by themselves establish complete conformance.

6. Accessibility feedback

If an accessibility barrier prevents you from completing an important task, please use the PurposePass accessibility contact form. Include the page or workflow, what you were trying to accomplish, your browser/device and assistive technology if relevant, and a description of the barrier. When practical, PurposePass will work to provide an alternative path while the issue is evaluated.