Accessibility

Accessibility statement

PreArrive targets WCAG 2.2 AA for the guest signing flow and core host workflow. The product is no-app by design, and guests must have a workable fallback when a device, camera, pointer, language, or assistive technology gets in the way.

Last updated May 22, 2026.

Guest signing flow

  • Keyboard-operable acknowledgments, buttons, language selector, and typed-signature fallback.
  • Screen-reader labels for rule and fee acknowledgments, signature methods, camera preview, consent, progress, and errors.
  • Visible focus states, large tap targets, mobile-first layout, and reduced-motion support.
  • Camera fallback path: guests are told to message the host through the booking platform so the photo requirement can be waived for that reservation.
  • Signature fallback path: guests can type their full name when drawing is inaccessible; the certificate records the method used.

Host workflow

  • Manual host-reviewed Spanish packet terms for rules and fees; no automatic translation of policy-sensitive text.
  • Guest preview for packet review, optional photo, signature, and signed/access-info states before sending.
  • Disclosure copy reminds hosts to provide an alternate acknowledgment path in the booking-platform message thread.
  • Arrival-release controls keep safety information visible even when other arrival details are held until signing.
Reporting an accessibility issue

Email [email protected] with the page, device/browser, assistive technology if relevant, and what blocked completion. If a guest cannot complete a signing packet, the host can use the booking-platform message thread as the alternate acknowledgment path.