Bug 472809

Summary:	Improve Train Accessibility Filtering in KDE Itinerary
Product:	[Applications] KDE Itinerary	Reporter:	reportthebug <chris.seiferth>
Component:	general	Assignee:	Volker Krause <vkrause>
Status:	REPORTED ---
Severity:	wishlist
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Android
OS:	Android 12.x
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description reportthebug 2023-07-30 19:54:05 UTC

As a user of KDE Itinerary, I would like to request the following feature to improve the accessibility filtering for trains:
Feature Request:

- Add a new filter option for "Accessibility" in the search bar, allowing users to select specific types of accessibility features they require, such as wheelchair accessibility or bike storage.
- Provide a clear and concise description of the accessibility features available at each train station, including information on the availability of elevators, ramps, and accessible restrooms.
- Provide a map view of the train station and the surrounding area, highlighting the location of accessible entrances, exits, and amenities.

Benefits:
This feature would greatly improve the accessibility and usability of KDE Itinerary for users with disabilities, allowing them to easily find and book trains that meet their needs. It would also help to reduce frustration and anxiety associated with traveling with a disability, and increase the overall user experience as well as help travelers with a bike.

Comment 1 Volker Krause 2023-07-31 15:24:02 UTC

Yes, that's definitely things we would like to have eventually!

For anything vehicle-based the necessary data for this is often not available in machine readable form and/or with a sufficient level of detail. Things are improving, but slowly (and there's EU regulation supporting that AFAIK).

On the ground the situation is better, we rely on OSM there as well as the elevator live status data also used on wheelmap.org. The train station indoor map we use can be customized using MapCSS style sheets, so doing use-case specific map styles is possible without too much effort.

Putting both parts together theoretically possible, but highly non-trivial. E.g. automatically inferring from "arrival on platform 5" whether there's a working elevator or step-free way out of the station. That essentially needs full indoor routing, something we definitely want but we are still quite a bit away from.