Featured Article
Compliance
A travel booking workflow should provide usable ways to complete the task when a person cannot hear, speak to or operate its voice interface. Adding a voice agent does not by itself establish accessibility or legal compliance.
This page previously contained material about California privacy law that did not match its accessibility topic. It now focuses on practical accessibility review. It is not a certification of any ConversAI Labs deployment.
Review the whole booking journey
Check entry, traveller details, itinerary choices, corrections, confirmation and support. Identify where the flow requires speech, hearing, a pointer device or a timed response. Include alternate routes in the test plan rather than reviewing the voice conversation alone.
For the web portion, the US Department of Justice guidance on web accessibility discusses barriers including inaccessible forms, missing text alternatives and mouse-only navigation. Its page also directs readers to newer requirements for state and local governments; determine which rules apply to your service with appropriate advice.
Make the alternate route usable
Provide an accessible text or assisted route suitable for the task. A visible alternative is not enough if it loses the request details or cannot complete the same booking step. Explain how to request assistance and how an unresolved case reaches a person.
Test corrections and confirmations
Check whether a traveller can correct a date, destination or passenger detail before the next action. Keep the recorded result available through an appropriate accessible channel. Verify the destination booking record rather than relying on a spoken acknowledgement alone.
Combine technical and human review
Include keyboard navigation, clear labels, understandable validation messages and relevant assistive-technology checks for the web interface. Test voice failure and the alternate route with participants whose access needs inform the design.
The DOJ guidance cautions that automated checks alone do not establish accessibility. Record the tested paths, unresolved issues, owner and retest date. Keep a way for users to report a barrier.
Connect the result to an accountable next action
If a voice call cannot complete the task, preserve the request under your data-handling rules and assign the next action. Use the workflow guide to design result handling and consult the API reference for supported operations.
About ConversAI Labs Team
The ConversAI Labs team writes about building and operating voice AI workflows.