Service Robots, Public Interaction, and Disability Access

Identify the service and setting

A hotel delivery robot, retail guide, restaurant server, reception kiosk, and hospital logistics platform perform different services. The assessment should identify who operates the facility, what the robot does, whether people must interact with it, and how equivalent human assistance or another method is provided where required.

The robot's route and interface should be considered together. A technically usable screen does not solve a blocked accessible route, while an unobstructed route does not make a voice-only transaction usable by every person. Product demonstrations should reflect the actual environment and service.

Physical access and safe movement

Part 36 addresses public accommodations within its scope, including maintenance of accessible features. Texas Human Resources Code § 121.003 addresses public-facility access and specified disability protections. A mobile robot should be assessed for interference with doors, elevators, corridors, service-animal movement, and emergency access under the applicable requirements. [1, § 36.211; 2]

Recommended testing includes wheelchairs, mobility aids, people moving unpredictably, low visibility, crowded areas, and stalled equipment. The assessment should identify who can move or secure a disabled robot without blocking a route indefinitely. These are deployment methods supporting actual obligations, under the cited accessibility authorities.

Communication and policy modifications

Section 36.303 addresses auxiliary aids and effective communication under its conditions, and § 36.302 addresses reasonable policy modifications and service animals. The facility should evaluate how a person receives instructions, identifies the correct robot, requests assistance, completes a transaction, and responds to an emergency. [1]

A standard app or screen should not be presumed sufficient for everyone. The legal inquiry includes the nature and context of the communication and applicable defenses or limits. The facility should avoid a default rule that automatically denies service whenever a customer cannot use the automated interface. The actual accommodation and operational facts matter.

Product and premises responsibility

Consumer-product jurisdiction, Texas product liability, negligent deployment, and premises duties require separate analyses. A robot sold for public interaction is not automatically a consumer product under the CPSA; the statutory definition and exclusions control. Covered product hazards can raise reporting duties even before a recall is announced. [3; 4]

The facility should identify route approval, maintenance, cleaning, charging, software changes, and complaint handling. A vendor contract can allocate tasks but does not automatically determine every duty to a visitor. Product-defect elements and negligence causation must be established under the actual claim rather than inferred from the robot's presence. [5]

Data and AI interaction

The robot may record voices, images, assistance requests, and location. CUBI and TDPSA require the actual data, entity, purpose, and exception analyses. A person seeking disability assistance should not be assumed to consent to unrelated biometric identification or marketing. The same interface can collect sensitive information that deserves separate handling. [6; 7]

TRAIGA includes specific governmental and health-care disclosure requirements. It does not impose the same notice on every private service robot solely because it uses AI. The actual actor and interaction should be identified before selecting the notice and timing. [8]

Standards and operational review

ISO 13482 can be relevant to personal-care robots within its publisher-defined scope, but should not be described as a universal law governing every hospitality machine. Actual licensed clauses and product scope are needed for a conformance claim. [9]

Recommended review includes complaints, near misses, route changes, interface updates, and whether the alternative service works in practice. A robot deployed successfully in an empty lobby may behave differently during a convention or emergency. The facility should identify who can restrict or suspend use when the original assumptions fail.

Hypothetical hotel deployment

A hotel uses a robot to deliver items but requires every guest to hear a spoken code and retrieve the item quickly from a small compartment. The facility should assess communication, reach, timing, assistance, and safe access for actual guests. The robot's ability to reach the room does not establish that the service is accessible to the person receiving it.