Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Identifying Automated Driving Systems-Dedicated Vehicles (ADS-DVs) Passenger Issues for Persons with Disabilities
This article summarizes findings from SAE Information Report J3171, which provides a literature review and expert interview results on universal design principles for Automated Driving Systems-Dedicated Vehicles (ADS-DVs). The report specifically addresses how to accommodate users who cannot obtain a driver’s license due to visual, mild cognitive, or certain physical impairments. It is scoped to fleet-operated on-demand shared mobility scenarios, anticipated to be the initial deployment mode for ADS-DVs.
🛠️ The report stresses that universal design must be embedded from the start of vehicle development to avoid costly retrofitting and to ensure safe, comfortable access for all passengers.
Understanding the Scope of SAE J3171
SAE J3171 focuses on Level 4 and 5 automated driving systems as defined by SAE J3016. Its scope is deliberately limited to fleet-operated, on-demand shared mobility, excluding fixed-route transit and private ownership. The report does not cover wheelchair lifts, ramps, or securements, as these are handled by other SAE committees. Engineers designing ADS-DVs must consider the diverse needs of passengers with disabilities who are currently unable to drive conventional vehicles.
Key Design Considerations for Accessibility
The report identifies critical design areas based on disability type. The table below summarizes key requirements for human-machine interface (HMI) and vehicle design:
| Disability Type | Key Design Requirements | HMI Considerations |
|---|---|---|
| Visual Impairments | Non-visual feedback (auditory, tactile); clear navigation cues | Speech input/output, haptic alerts, audible destination confirmation |
| Cognitive Impairments | Simplified interfaces; reduced cognitive load; consistent patterns | Icon-based controls, step-by-step guidance, simple language |
| Physical Impairments | Accessible controls; adequate space; easy ingress/egress | Voice control, adjustable seating, high-contrast buttons, low-force mechanisms |
🔍 Understanding specific impairments is essential. For instance, visually impaired passengers need auditory or tactile cues instead of visual displays, while those with cognitive impairments benefit from predictable interfaces and minimal distractions.
Engineering Insights for Inclusive ADS-DVs
Universal design principles—equitable use, flexibility, simplicity, perceptible information, tolerance for error, low physical effort, and size/space for approach—form the foundation. Stakeholder interviews in the report highlight that collaboration with disability advocates is critical to avoid common mistakes, such as focusing only on physical access while neglecting cognitive or sensory needs.
⚠️ A common pitfall is assuming a one-size-fits-all approach. Inclusive testing with actual users from various disability groups ensures that vehicle interfaces and layout are genuinely accessible.
Additionally, engineers must consider the “last mile” challenge: ensuring easy vehicle location and access. Fleet booking systems should be accessible via multiple channels (phone, app, web) and support assistive technologies.
Frequently Asked Questions
- What is the primary focus of SAE J3171?
- The report identifies passenger issues for persons with disabilities in ADS-DVs through literature review and expert interviews, emphasizing universal design.
- What disabilities are specifically addressed?
- Visual, mild cognitive, and physical impairments that prevent obtaining a driver’s license. Guidance can extend to other disabilities.
- What is not covered in this report?
- Fixed-route transit, private vehicle ownership, wheelchair lifts, and securements are outside its scope.
- Why is universal design important for ADS-DVs?
- It ensures vehicles are usable by all without adaptation, promoting independence, safety, and equitable access to mobility for non-driving passengers.
For full details, refer to the SAE J3171 document.
