Campgrounds and RV parks sell a numbered, non-interchangeable inventory through a website, and the way most of them do it is one of the least accessible patterns on the web: an interactive park map where the guest clicks a pin to pick a specific site. Around that map sits an availability calendar that signals open dates by color, a rate and amenity table comparing tent sites to full-hookup pull-throughs, a park guide and trail map published as a scanned PDF, seasonal and annual site contracts, and an account portal for modifying or cancelling a reservation. For this industry the accessibility problem is not abstract, because the guests most likely to need detailed accessibility information about a site, including wheelchair users evaluating whether a pad is paved and whether the bathhouse route is navigable, are exactly the guests a clickable-map booking flow shuts out. There is also a federal rule aimed squarely at this business: places of lodging must describe their accessible features in enough detail for a guest to independently assess whether they meet their needs, and must allow accessible sites to be reserved through the same methods and on the same terms as everyone else, which makes the common practice of listing accessible sites as call-to-book a direct violation. Publicly owned campgrounds run by a city, county, state park system, or federal agency carry Title II obligations on top of that. This guide covers the legal requirements, the most common failures, and a practical compliance checklist for campgrounds and RV parks.

Legal Requirements

Key Accessibility Issues in Campgrounds & RV Parks

Interactive Site-Selection Maps With No Text List of Sites

The defining campground booking pattern is a park map image with clickable numbered pins, where the guest hovers to see a tooltip and clicks the pin to select a site. These maps are typically image-based with no accessible names on pins, unreachable by keyboard, dependent on hover to reveal site details, and offer no non-map path to the same inventory. A blind, low-vision, keyboard-only, or motor-impaired guest simply cannot choose a site and complete a booking, which blocks the entire product rather than degrading it.

How to fix:

Provide a keyboard-accessible text list or table of every site as real HTML alongside the map, with site number, type, length, hookups, surface, and price, and make it the equivalent path to the same booking action. Give map pins accessible names and keyboard focus, never require hover to reveal information (WCAG 2.2 1.4.13), and ensure the selected site is announced as text (see store locator map guidance).

Accessible Sites Not Described in Detail or Bookable Only by Phone

Accessible campsites and cabins are frequently listed as nothing more than an ADA icon on a map pin, with no description of pad surface, grade, width, transfer space, table and fire-ring clearance, or the route to the bathhouse. Many parks then remove those sites from the online inventory entirely and instruct guests to call. That is the exact combination the lodging reservations rule prohibits, because the guest can neither independently assess whether the site works nor reserve it on the same terms as everyone else, and it forces a disabled guest into a slower channel where the site may already be gone.

How to fix:

Publish a detailed text description of every accessible site covering surface, slope, dimensions, clearances, accessible features of the bathhouse and route, and any known barriers, and make accessible sites bookable online through the same flow, terms, and cancellation policy as all other sites (28 CFR 36.302(e)). Hold accessible sites out of general inventory until comparable sites are sold, and never replace a description with an icon alone (1.4.1).

Availability Calendars and Date Pickers That Signal Open Nights by Color Alone

Multi-night campground stays depend on a calendar showing which nights a specific site is free, often with green, yellow, and red cells and a drag-to-select range interaction. These calendars commonly convey availability through color alone, cannot be operated by keyboard, trap focus, fail to announce the selected arrival and departure dates, and silently reject invalid ranges such as a minimum-stay weekend. A colorblind guest misreads availability and a screen reader user cannot tell which nights are open on the site they want.

How to fix:

Make the calendar fully keyboard operable, announce each date's availability, price, and minimum-stay status as text rather than color alone (WCAG 2.2 1.4.1), and expose the selected range programmatically. State minimum-stay and check-in rules as readable text before submission, announce rejected ranges as errors linked to the field (3.3.1), and confirm the held reservation with an accessible status message (4.1.3) (see date picker guidance).

Rate, Hookup, and Amenity Tables Built as Layout Grids or Images

Guests compare site classes by hookup type, rig length limits, seasonal rate, and amenities, and this comparison is usually rendered as a styled div grid with no table semantics, an image of a rate sheet, or a table with no header cells. Screen reader users hear a stream of disconnected numbers with no way to tell which rate belongs to which site class, and a guest with a thirty-eight-foot rig cannot determine which sites accept their length, leading to a booking that cannot physically be honored on arrival.

How to fix:

Use real HTML table markup with th elements, scope attributes, and a caption so every rate and amenity is programmatically tied to its site class (WCAG 2.2 1.3.1). Never publish rates or hookup details only as an image, keep tables readable when zoomed to 400 percent by allowing horizontal scroll rather than clipping (1.4.10), and make any comparison filter keyboard operable (see accessible tables guidance).

Park Guides, Trail Maps, and Rules Published as Scanned PDFs

Campground rules, check-in instructions, trail and facility maps, seasonal contracts, and pet and quiet-hour policies are commonly posted as scanned or untagged PDFs, sometimes reached only through a QR code on a sign at the gate. A scanned document is an image, so a screen reader announces an empty page, and a guest with low vision cannot enlarge it without losing the layout. Since these documents carry the rules a guest is contractually bound to follow and the accessibility information for the facility, an unreadable PDF withholds material terms from disabled guests.

How to fix:

Publish rules, check-in instructions, policies, and facility information as HTML pages as the primary format, keeping any PDF as a secondary convenience copy that is tagged, text-based, and has a correct reading order and document title (WCAG 2.2 1.3.1, 1.3.2). Give trail and facility maps a text description of routes, grades, and accessible facilities, and pair every QR code with a readable short URL and the same content on the web (see accessible PDF and QR code guidance).

Compliance Checklist

  • Every site is listed in a keyboard-accessible text list or table alongside the map, with the same booking action available from the list
  • Map pins have accessible names, take keyboard focus, and never require hover to reveal site details
  • Every accessible site has a detailed text description of surface, slope, dimensions, clearances, and the route to accessible facilities
  • Accessible sites are bookable online through the same flow, terms, and cancellation policy as all other sites, with no call-to-book requirement
  • Accessible sites are held out of general inventory until all comparable non-accessible sites of that type are reserved
  • The availability calendar is keyboard operable and announces availability, price, and minimum-stay status as text rather than color alone
  • Selected arrival and departure dates are announced, and rejected date ranges produce an error linked to its field
  • Rate, hookup, and amenity comparisons use real table markup with header cells and are never published only as an image
  • Rules, check-in instructions, policies, and facility information are available as HTML, with any PDF tagged and text-based
  • Trail and facility maps have a text description of routes, grades, and accessible facilities, and every QR code has a readable URL alternative

Further Reading

Other Industry Guides