Building Better Accessible Transport Maps in Thailand
A crowdsourced map of accessible public transport routes for persons with disabilities in Thailand could turn fragmented travel information into practical, local knowledge. For a wheelchair user, a step-free station is only useful if the footpath leading to it is passable, the lift works, the platform gap is manageable and the next interchange is accessible.
The concept fits ICTD-ASP’s role as a development platform linking governments, technology companies, civil society and funding partners. It combines mobile reporting, open transport data and community verification to support more independent travel, stronger public services and better investment decisions across Thailand.
Why Accessible Travel Information Matters
Thailand’s transport networks vary sharply between Bangkok, regional cities and rural areas. Bangkok has expanding BTS Skytrain and MRT routes, but station access, footpaths and interchange conditions can differ from one location to the next. In Chiang Mai, Phuket and other tourism centres, buses, songthaews and informal services may be easier to find than reliable accessibility information.
A route planner designed for disabled travellers should account for the whole journey rather than simply marking a station as accessible. It could record lift outages, steep kerbs, narrow pavements, tactile paving, accessible toilets, boarding assistance and the availability of low-floor vehicles. These details would help wheelchair users, people with limited vision, older passengers and families travelling with mobility aids.
The wider benefit is improved planning. Transport agencies could see repeated reports about broken ramps or inaccessible interchanges, while local authorities could identify missing links between housing, hospitals, schools, markets and employment areas. Reliable evidence can support targeted upgrades instead of relying on occasional audits.
Turning Local Experience Into Usable Data
The platform could allow passengers, disability organisations, transport workers and volunteers to submit location-based updates through a mobile app or lightweight web form. Reports might include a photo, a short description, a time stamp and a simple classification such as “step-free”, “limited access”, “temporarily blocked” or “needs assistance”.
Crowdsourcing needs a verification system so the map remains dependable. Multiple reports could increase confidence, while trained community reviewers could check sensitive or disputed information. Transport operators could confirm planned lift maintenance, route changes and vehicle availability through an agency portal.
The map should offer several travel modes. A passenger might select wheelchair-accessible routing, low-vision support, reduced walking, quiet transfers or assistance-required travel. Data should be available in Thai and English, with clear icons and plain language. Audio prompts, high-contrast screens and compatibility with screen readers would make the service useful beyond its primary audience.
Designing For Safety, Privacy And Inclusion
Accessibility information can affect personal safety, so the platform should avoid publishing unnecessary details about individual users. Anonymous submissions, limited location precision for personal reports and clear data-retention rules would reduce privacy risks. Users should be able to report hazards without exposing their identity.
The project should involve disabled people from the design stage, with paid advisory roles rather than one-off consultation. Organisations representing wheelchair users, people with psychosocial disabilities, blind and low-vision communities and older people can identify practical barriers that a technical team may miss.
A strong governance model would define who owns the data, who can amend official route information and how complaints are handled. The platform should distinguish between community observations and operator-confirmed information. That distinction helps passengers judge whether a report is recent, reliable and suitable for a time-sensitive journey.
Lessons From Australia’s Transport Market
Australian users will recognise the value of journey-level information from systems such as Transport for NSW, Public Transport Victoria and Translink in Queensland. In Sydney, an accessible train station may still present difficulties if a lift at Central or a connecting footpath is out of service. In Melbourne, tram accessibility can depend on the stop platform, vehicle type and street conditions, making a route label too general for many passengers.
The Australian market also shows why open standards matter. GTFS and GTFS-Realtime feeds can support route planning, while operator data, council works notices and community reports add detail that scheduled feeds often miss. A map that combines these sources could serve as a practical layer between official transport information and the lived reality of getting from a front gate to a destination.
Local language matters too. Australians commonly say “footpath” rather than “sidewalk”, and people may describe a route as “pram-friendly” or suitable for a mobility scooter. These everyday terms can help shape user testing and search functions. Partnerships with councils, disability advocacy groups, universities and transport technology firms would reflect how the Australian market often combines public procurement with specialist private suppliers.
Building A Sustainable Partnership Model
ICTD-ASP could help bring together Thai transport authorities, municipal governments, telecommunications providers, mapping companies, universities and disability organisations. An initial pilot might focus on Bangkok, then expand to Chiang Mai, Phuket and selected provincial towns. Testing across dense urban routes and lower-frequency regional services would reveal different data and connectivity needs.
The system should work with intermittent internet access and affordable smartphones. SMS or call-centre reporting could complement app submissions where data access is limited. Training workshops for community mappers would build local capacity, while small grants could support disability organisations that verify information in their neighbourhoods.
A clear financing model is essential after the pilot period. Public agencies could fund core data services, operators could contribute live service information, and development partners could support inclusive design and technical infrastructure. The following comparison shows how each information source contributes to a dependable accessibility map.
| Information source | Strength | Limitation | Best use |
|---|---|---|---|
| Official transport feeds | Consistent routes, stops and timetables | May omit physical barriers or temporary faults | Base network and scheduled services |
| Passenger reports | Captures real conditions quickly | Requires moderation and verification | Lift outages, kerbs, blocked paths and boarding conditions |
| Disability organisations | Specialist knowledge and community trust | Coverage may vary by location | Testing, validation and priority setting |
| Operator updates | Useful for maintenance and service changes | May focus on vehicles rather than complete journeys | Live alerts and confirmed disruptions |
| Local government data | Shows footpaths, crossings and public works | Data formats may differ between agencies | First- and last-mile accessibility |
A successful map should be judged by whether it helps someone complete a journey with fewer surprises, not by the number of pins displayed. The essential measure is trustworthy, current and human-centred information that connects transport networks with the streets, buildings and services around them.