Inspiration
The inspiration for Accesimap stems from the need to bridge the information gap for people with accessibility needs. Many public spaces lack detailed, reliable, and up-to-date accessibility information, leaving individuals with disabilities, seniors, or parents with strollers to face uncertainty or barriers when navigating stores, restaurants, parks, or transit stations. Existing solutions, like static accessibility guides or incomplete venue websites, often fail to provide granular, real-world insights. Accesimap aims to create a dynamic, community-driven platform where users share firsthand experiences, fostering inclusivity and empowerment. The vision is to build a global resource that not only informs but also builds a supportive community advocating for universal accessibility.
What it does
Accesimap is an interactive, crowdsourced platform that maps the accessibility of public spaces worldwide. Users contribute detailed reviews, ratings, and photos of accessibility features (e.g., ramps, elevators, accessible restrooms, sensory-friendly areas) for locations like stores, restaurants, parks, and transit stations.
How we built it
While this is a conceptual explanation, the development of Accesimap would involve:
Frontend: A user-friendly interface built with frameworks like React or Vue.js, integrated with a mapping API (e.g., Google Maps or OpenStreetMap) for the interactive map. Accessibility features like screen reader compatibility and keyboard navigation would be prioritized to ensure the platform itself is inclusive. Backend: A robust backend using Node.js, Django, or similar frameworks, with a database (e.g., PostgreSQL) to store location profiles, user data, and reviews. APIs would handle data retrieval and updates. Crowdsourcing Mechanism: User authentication and contribution systems built with secure protocols (e.g., OAuth). Features like photo uploads and review submissions would use cloud storage (e.g., GCP). Moderation System: A combination of automated tools (e.g., keyword filters for inappropriate content) and human moderators to review flagged content. Mobile App: iOS and Android apps developed using Flutter or React Native for on-the-go access, integrating geolocation for "nearby" searches. Accessibility Standards: Compliance with WCAG (Web Content Accessibility Guidelines) to ensure the platform is usable by all, including those with visual, auditory, or motor impairments.
Challenges we ran into
Building Accesimap would present several challenges:
Data Accuracy and Moderation: Ensuring user-submitted information is accurate and up-to-date is difficult. Incorrect data could mislead users, so a robust moderation system (automated and human) is needed, which is resource-intensive. User Engagement: Encouraging consistent contributions from a diverse user base is challenging. Low participation could limit the platform’s coverage, especially in less populated areas.
Accomplishments that we're proud of
Assuming a successful initial rollout, the team behind Accesimap would take pride in:
Community Impact: Creating a platform that empowers thousands of users to navigate public spaces confidently, improving their quality of life. Comprehensive Database: Building a growing, reliable repository of accessibility information for diverse locations, from urban transit hubs to rural parks.
What we learned
The development process would yield valuable insights:
User-Centric Design: Iterative feedback from users with disabilities is critical to creating a truly inclusive platform. Moderation Balance: Striking a balance between automated moderation and human oversight is essential to maintain trust and accuracy without overwhelming resources.
What's next for Accesimap
The future of Accesimap would focus on growth and innovation:
Global Expansion: Increase coverage by partnering with local disability organizations and incentivizing contributions in underserved areas. AR/VR Integration: Develop augmented reality features to provide real-time accessibility navigation (e.g., overlaying ramp locations in a user’s field of view).
Built With
- gcp
- mysql

Log in or sign up for Devpost to join the conversation.