Accessibility Statement

heycupo aims to make its booking platform usable by people who rely on assistive technologies, people with motor or cognitive differences and people using the service in difficult travel conditions.

Standard

heycupo targets WCAG 2.1 Level AA across:

• Marketing pages.
• Public booking pages.
• Checkout, confirmation and cancellation flows.
• Operator web dashboard.
• Installed PWA dashboard shell.
• Transactional emails, including QR ticket emails.

The native mobile app targets the iOS and Android accessibility baselines: screen reader labels, font scaling where practical, high contrast, reduced motion and touch targets that work on real phones.

Current conformance

heycupo self-assesses as partially conformant with WCAG 2.1 AA as of this statement. We have not commissioned a third-party accessibility audit yet.

Known gaps

• Some date and time pickers may still be harder to use with screen readers than native controls.
• Some live status changes, like payment confirmation or booking holds, may not announce immediately to assistive technologies.
• Dashboard charts need stronger non-colour alternatives.
• Uploaded photos use fallback alt text until operator-written alt text exists.
• QR scanning in the dashboard depends on browser camera APIs, so manual ticket-code entry is always provided as a fallback.

What already works

• Keyboard navigation across main web flows.
• Semantic headings, landmarks, lists and labels.
• Focus-visible rings on interactive elements.
• High contrast on primary text and actions.
• Reduced-motion respect for CSS animations.
• Zoom to 200% without breaking the main booking and legal flows.
• QR ticket emails include the written ticket code as text, not only a QR image.
• Manual code entry exists anywhere camera scanning may fail.
• Pages and emails set language attributes where the locale is known.

Reporting an issue

Email hello@heycupo.com with:

• What page, email or app screen had the issue.
• What you were trying to do.
• Your browser, device and assistive technology if relevant.
• A screenshot or screen recording if easy.

You can also reply to any heycupo transactional email and put "accessibility" in the subject.

heycupo aims to respond within 5 business days and prioritises issues that block booking, payment, sign-in or ticket use.

Last evaluation

This statement was last revised on 2026-04-27 after the mobile web PWA dashboard and scan fallback were added.

heycupo. Lisbon, Portugal. Last updated: version v2, effective 2026-04-27. See also the Privacy Policy and Booking Terms.