Paper Boat Media / Theaters, music venues, event spaces & entertainment

An ADA Website Demand Letter for Your Theater or Event Venue?

An available seat is not an available experience if a guest cannot identify it, select it or complete the purchase.

Your theater, music venue or event space receives an ADA website demand letter. You have considered entrances, seating locations, routes and restrooms. The letter alleges that someone could not use the website to access information, obtain a ticket or make an inquiry.

For a venue operator, the difficulty is that the website may not be a single system. A promoter supplies the event description, a ticketing company controls the seat map and checkout, and your team manages the building and guest service. A customer experiences one event, while the work is divided among several organizations.

Begin with qualified counsel's assessment of the notice. The allegations require investigation; the letter's existence is not a legal determination. Preserve relevant pages, configurations and records through a coordinated process, then establish what the customer was trying to do.

I am Rob Urban of Paper Boat Media. I would prefer our introduction to involve stronger event demand, better venue positioning or a more profitable calendar. I also work with businesses when a difficult challenge needs attention. In this situation, I can help organize the website and customer-experience work while your attorney handles legal advice and the response to the claim.

Separate the seat from the way it is sold

Physical seating arrangements and digital purchasing are connected, but they are not the same question. A venue may offer accessible seating while the online interface makes it hard to identify or purchase. A usable checkout does not establish that the underlying seating policies are appropriate.

The DOJ's ticket-sales guidance addresses the sale of accessible seats through comparable methods, hours and sales stages, along with information and related requirements. Counsel and operations should assess how those provisions apply to the venue and event. The website review should examine how the approved policy is implemented.

That distinction matters for a presale. If the event's general audience can buy online during a particular window, the treatment of accessible-seat purchases should be reviewed rather than assumed correct because a box-office phone number appears somewhere on the page.

Likewise, the website consultant should not invent eligibility requirements, ticket limits or proof-of-disability requests. Those are policy decisions with legal consequences. The technical assignment is to expose and repair barriers in the approved process and flag questions for the responsible professionals.

The seating map is not the whole interface

A map offers a visual relationship between stage, sections and seats. It can also become a demanding interaction: zoom, pan, choose a section, inspect a seat, select a quantity and distinguish what remains available. A person using a keyboard or screen reader needs a workable method of making the relevant choices.

Do not assume that adding a text label to the map solves the purchase. The actual seat options, prices, accessible features and selection state need evaluation. If the provider offers a list view or another supported method, test whether it conveys enough information and reaches the same practical outcome.

Test the decision the guest needs to make

An illustrative patron wants two seats together, including a location with specific accessible features. Can the patron identify the relevant options, understand the relationship between the selections and review the final purchase? Does the interface make clear when a chosen place is no longer available?

The review should include the circumstances that make ticketing difficult: limited inventory, a seat released during the purchase, an unavailable adjacent seat and a change in quantity. These are normal sales conditions. A test of an empty auditorium misses much of the work.

Be precise about what the ticketing provider can represent. A generic accessible icon may not convey the detail someone needs. Operations should supply verified information, and the interface should present it without making the guest interpret promotional language or guess from a map.

A visual cue needs a usable equivalent

Seat colors, symbols and hover panels often carry important information. Check what happens when the visitor cannot hover, cannot distinguish the colors or enlarges the interface. Confirm that the selected state and next action remain understandable.

W3C's guidance on complex images is useful background for information-rich visuals. A transactional seating system requires additional interaction testing; an image description alone is not a replacement for usable selection controls.

Follow the ticket after checkout

The purchase is incomplete from the guest's perspective until they can identify and use what they bought. Review the confirmation, ticket delivery, account requirements and any instructions for entry.

A ticket PDF, mobile wallet link and account-based ticket can each introduce different barriers. Do not assume that a working web checkout covers the later format. The scope should state which delivery methods and customer tasks are evaluated.

Test appropriate error and recovery states using approved arrangements. A payment failure should not leave the customer uncertain whether the seats remain held or whether a charge occurred. If a timed hold applies, its behavior and communication need examination against the relevant technical criteria and business conditions.

Use a provider-supported test environment or a controlled process agreed with the venue. Avoid consuming scarce seats or creating real charges without authorization. The operations team should know which records are tests and how they will be cleared.

Refunds, exchanges and transfers also deserve consideration where offered. A guest who successfully buys a ticket may later be directed into a different system to change it. Include those handoffs in the inventory instead of discovering them only after a complaint.

The promoter, provider and venue need a shared issue record

Identify who owns event descriptions, inventory configuration, seat information, checkout and guest communications. A contract may allocate responsibilities, but counsel should interpret that allocation. For implementation, the team still needs to know who can actually make each change.

An actionable issue report describes the event configuration, affected task, steps and observed behavior. It names the party responsible for the next action and the person coordinating the response. It also distinguishes confirmed defects from issues awaiting access or additional information.

Vendor accessibility documentation should be matched to the product and version in use. Ask whether it covers the interactive map, hosted checkout, account experience and delivered tickets. A statement about the provider's marketing website is not evidence about your configured sales flow.

If a supported configuration change is proposed, test it with the venue's actual event types. A general-admission configuration and a reserved-seating production have different needs. A festival pass with multiple event entitlements introduces another layer.

Review planning: Theaters, music venues, event spaces & entertainment
Event configurationA distinct concern to investigate
Reserved seatingSeat information, selection, companion arrangements and inventory changes
General admissionTicket categories, quantity, dates and admission conditions
Subscription seriesMultiple performances, retained selections and account management
Festival or multi-day passIncluded dates, add-ons and redemption instructions
Private event inquiryVenue information, availability requests, documents and staff response

A venue rental is a different transaction

An event space may receive a website allegation even when it does not sell public tickets. Its key action may be requesting a tour, downloading a package or asking about a date.

Review how a prospective organizer understands the space. Capacity, layouts, services and practical access information should be based on approved facts. A beautiful brochure may still be difficult to read, and an image of a floor plan may not explain the options adequately.

The inquiry form should make its purpose clear. Is the organizer reserving a date or asking whether it is available? Does the confirmation explain what happens next? Are file uploads, date selection and required fields usable?

The commercial stakes are different from an individual ticket sale. One inaccessible inquiry process can interfere with a substantial event opportunity. Prioritization should consider the importance of the task, not only its traffic volume.

Florida context without a generic legal promise

The relevant analysis depends on the venue, operator, allegation and governing law. Government-operated facilities require a separate framework from private-business claims. My ADA website demand-letter guide discusses Florida context and general response considerations, while the Title II guide addresses government web requirements.

Do not treat repairs as a promise of legal closure. Counsel should handle proceedings, agreements and commitments. The technical team should provide accurate information about what changed, what was verified and what remains unresolved.

Similarly, an automated score or accessibility plug-in is not a complete evaluation of seating and ticketing. My software guide explains the purchasing question. The venue's acceptance test should follow the actual guest action.

Make accessibility part of the event setup

The next production can undo careful work if event configuration is treated as a purely administrative task. Establish a repeatable release check for event descriptions, seat information, pricing, ticket options and confirmations.

Give the team a small set of representative journeys to verify when a new event type is introduced. Retest material vendor changes. Keep reports from the box office and guest-services staff connected to the people responsible for the website.

For a remediation engagement, define the agreed technical target and scope. Prioritize barriers to essential tasks, then examine shared components and related states. My remediation guide describes how to turn findings into an ordered plan.

The deliverable should include an intelligible handover: implemented changes, retest evidence, vendor tickets, unresolved items and ownership of future checks. A venue needs something it can use when the next onsale approaches.

The commercial conversation remains larger than the letter

A venue's profitability depends on many decisions: which events it attracts, how clearly it communicates value, how efficiently it handles inquiries and whether guests want to return. Website accessibility intersects with that experience without replacing the broader strategy.

I can help with both the immediate problem and those larger questions. The work should remain transparent. An urgent repair has a defined scope; a positioning, marketing or commercial strategy engagement should be proposed because it serves the business.

I would like the next conversation to be about a promising season or a stronger pipeline of events. A careful response to the present challenge can be the first step toward that working relationship.

Questions from venue operators

Does this concern the building or the website?

Read the allegations carefully. A matter can involve digital interaction, seating policy, physical features or more than one issue. Assign the right professionals to each question instead of assuming a website change resolves all of them.

Can accessible-seat purchases be handled only by phone?

Do not assume that is sufficient. The DOJ ticket-sales guidance addresses comparable sales methods and conditions. Counsel should assess the venue's arrangements and the team should examine the actual purchase process.

Can you change our ticketing company's code?

Direct implementation depends on access and control. I can help document the problem, identify the responsible provider and coordinate a repair and retest. The scope should state those dependencies clearly.

What if we only rent the venue for private events?

Review the inquiry and booking journey you offer, including packages, forms and documents. That is a different task from purchasing a theater seat and deserves its own evaluation.

Is a seat-map description enough?

Not necessarily. Guests also need a usable way to select and purchase appropriate tickets. Review the information and the interaction together.

Can you help with event demand and venue marketing too?

Yes. My broader work includes growth strategy, positioning, marketing and customer experience. We can discuss those opportunities while keeping the immediate remediation commitments clear.

Bring the event and the systems into the same conversation

Contact me with the public website address, ticketing provider and the kind of event or inquiry involved. We can agree how to handle further technical records and counsel coordination before sensitive material is shared.

My website accessibility consulting can help define the work, organize provider responsibilities and establish a meaningful verification process. The aim is a usable guest experience and a plan the venue can manage, with room for a better conversation about the business afterward.

Sources and scope

Reviewed October 20, 2026. Practical website and business guidance, not legal representation. All scenarios are illustrative.

Scroll to Top