Define the activity-booking journey
For a Denver business offering tours, equipment rentals, classes, or guided activities, the website often needs to communicate more than a price. A customer may need to understand dates, participant requirements, meeting details, availability, and cancellation terms before deciding whether to book.
The assessment should cover those decisions and the actual booking process. This guide uses hypothetical activity-booking scenarios; it does not report findings about a particular operator or make claims about physical accessibility.
Present meaningful information outside images
An attractive route map or equipment photograph can carry information that a customer needs. If a map communicates meeting locations or route choices, provide an equivalent text description appropriate to the task. If an image is only decorative, an empty alternative may be appropriate rather than a list of SEO keywords.
Describe participant requirements in understandable text. Do not rely on a small icon to communicate restrictions, refund rules, or necessary preparation. Whether the activity itself is accessible requires a separate operational assessment.
Booking step | Accessibility question | Verification task |
|---|---|---|
Compare activities | Are restrictions and included services available as text? | Read and compare two options without relying on images |
Choose dates | Is availability understandable without color alone? | Select and change a date with a keyboard |
Add rental items | Are options and quantities named and grouped? | Review the selections before payment |
Accept a waiver | Is the document readable and the agreement control usable? | Access the document and correct an omitted agreement |
Evaluate waivers and confirmation documents
A booking journey may include a waiver, a PDF, or an email attachment. A scan of the public page does not establish that the document has a sensible reading order or that a signature process is usable. List document review separately from HTML evaluation.
The confirmation should communicate the reservation details and next steps in an accessible format. An image-only confirmation or unexplained attachment may leave a customer unable to find meeting instructions.
Match repairs to the system you control
Identify whether a barrier belongs to your theme, a booking plugin, an embedded provider, or a document workflow. A confirmed source change can repair selected literal website elements. It cannot automatically correct a vendor's scheduling application or certify an activity's operational access.
After deployment, compare the affected public page with the proposed repair and repeat the booking task. Record what was tested, what was not, and whether a third-party provider remains responsible for an unresolved step.
Document technical work without legal promises
For a complaint, preserve the alleged barrier and relevant dates. Build a technical record that distinguishes reproduced issues from questions requiring manual evaluation. Do not infer the legal meaning of the complaint from a scan score; counsel should assess legal duties and response deadlines.
ADAFix provides remote website accessibility support, not a Denver office or legal representation. The DOJ's web-accessibility guidance and W3C evaluation resources are useful starting points, not a substitute for context-specific advice.
Questions Denver operators ask
Is an accessible booking page proof that the activity is accessible?
No. Website tasks, documents, venue conditions, equipment, and service delivery are different assessment scopes.
Can we ignore documents if our scan is clean?
No. Documents and signature workflows may be outside an automated HTML scan. Explicitly include them when they are required to book.
Where can we find the next checklist?
Read image-alternative guidance, review the technical complaint checklist, or browse Colorado coverage.