Legal · Last reviewed 2026-07-25 · Next review 2026-10-23

Accessibility statement

PickRV is committed to making the PickRV marketplace accessible to all users, including those with disabilities. We target WCAG 2.2 Level AA conformance and ADA Title III standards. This is our single public accessibility statement: our current progress, what it covers, our remediation roadmap, and how to report issues.

Current conformance: partial WCAG 2.2 Level AA

PickRV is currently undergoing systematic remediation toward full WCAG 2.2 Level AA conformance. The following components meet the standard:

· Touch targets 44×44 pixel minimum (most surfaces)
· Semantic HTML5 (header, nav, main, article, section)
· ARIA labels on all interactive elements
· Keyboard-navigable booking flow
· "Skip to content" link at top of every page
· Error messages announced via aria-live regions
· Reduced-motion preference respected on animations
· Color contrast ratio 4.5:1 on body text (where verified)
· Layout supports zoom and text resize to 200% without loss of content

Features built for assistive technology

Screen reader support

Compatible with NVDA, JAWS, VoiceOver, TalkBack. All images have alt text. Forms are properly labeled.

Keyboard navigation

All interactive elements reachable via Tab. Skip links at page top. Focus indicators visible throughout.

Voice assistant ready

Guides and listing summaries are structured so voice assistants (Alexa, Google Assistant) can read them aloud.

Mobile responsive

Designed mobile-first. Tested on iPhone SE (375px) and Android phones. Pinch-zoom enabled.

What this statement covers

This statement applies to:

· pickrv.com — the production web application and every path under it: search and discovery, listing pages, booking and checkout, traveler and host dashboards, the Help Center, and every legal and policy page.
· Transactional email — booking confirmations, receipts, verification prompts, host onboarding and policy notices. Templates are authored for screen-reader linearization, alt text on every image, and plain-text fallbacks.
· Editorial and marketing pages — state guides, park pages, category hubs, and content under /stories, /academy, /help and /wiki.

It does not cover:

· Third-party payment and identity flows rendered inside their provider's own iframe, which inherit that provider's accessibility posture.
· Native mobile apps, which will get their own statement at public launch.
· Profiles we keep on platforms we do not control, where the platform sets the accessibility floor.

Known limitations

We publish a candid list of known gaps because trust requires honesty. We are working to remediate the following:

· Some user-uploaded host photos may lack descriptive alt text (host-supplied content)
· Color contrast on certain legacy components is being audited
· Photo carousel zoom controls being upgraded for screen reader semantics
· Map view (MapLibre) keyboard navigation in active development — pan and zoom work, cluster expansion and pin selection still need a pointer
· The mobile date picker falls back to the native iOS control, which has known VoiceOver edge cases on some iOS versions

We target full WCAG 2.2 Level AA conformance by end of 2026 Q3.

Report an accessibility issue

If you encounter a barrier accessing PickRV, please contact us. We respond within 5 business days and remediate within 30 days of report when possible.

Email: support@pickrv.com

Mailing address: PICKRV LLC, 1647 Van Buren St, Hollywood, FL 33020, USA. You can also send accessibility correspondence to support@pickrv.com.

Please include the URL of the page, the assistive technology and version you use (for example "JAWS 2025 on Windows 11" or "VoiceOver on iOS 18"), and a description of the barrier. A screenshot or screen recording helps but is not required. If you would rather not email, open a ticket at Help.

How we review this

This statement is reviewed every 90 days. A review covers an automated accessibility scan of the main public routes, a keyboard-only walkthrough of the booking and checkout paths, a contrast check of anything shipped since the last review, and an update to the limitations list above.

Last reviewed: 2026-07-25 · Next scheduled review: 2026-10-23

Third-party surfaces

Payment and identity verification are rendered inside the provider's own embedded flow, and that provider's accessibility conformance governs those screens. Our map renderer is open source; we extend its keyboard support and ARIA labeling where the library exposes the hooks. Sign-in is rendered by our own components rather than a hosted widget, so its accessibility is owned by this codebase. We do not ship social embeds or marketing widgets that degrade the accessibility of the page hosting them.

Standards we conform to

· Web Content Accessibility Guidelines (WCAG 2.2 Level AA)
· Americans with Disabilities Act (ADA) Title III
· Section 508 of the Rehabilitation Act
· EN 301 549 (European accessibility standard)