Inspiration
Accessibility barriers often hide in everyday places: a curb without a ramp, an entrance with stairs only, or public information announced solely through audio. These seemingly small details can prevent someone from accessing essential services and participating in community life. I created AccessPath to explore how a clear, community-centered reporting experience can make such barriers visible and actionable.
What it does
AccessPath is a responsive community accessibility reporting prototype. People can document a barrier, describe its public location and impact, choose a category and urgency, and browse structured reports. A searchable board supports categories for mobility, vision, hearing, and other needs, with reported, in-review, and resolved statuses.
Working features
- Guided report creation with validation and privacy notice.
- Search, category filters, and status filters.
- Local saving and status updates for new reports.
- An illustrative interactive neighborhood map linking to example reports.
- Transparent, rule-based text suggestions that help categorize an issue and prompt useful details.
- Responsive design, semantic landmarks, keyboard-operable controls, visible focus states, and reduced-motion support.
Demo transparency: The six initial records are fictional examples, not verified real-world reports. Newly entered reports stay in the current browser's local storage; they are not shared publicly. The map graphic is illustrative, not real geographic routing. The suggestion helper is deterministic and does not call an external AI service.
How I built it
I designed and implemented AccessPath with semantic HTML5, CSS3, and vanilla JavaScript. The lightweight front end requires no credentials, frameworks, or build process. JavaScript handles filtering, form validation, localStorage persistence, report creation, and status changes. User-entered text is rendered as text, not HTML. The interface is organized around three straightforward jobs: understand accessibility issues, explore relevant reports, and document a barrier.
Challenges
The biggest challenge was balancing a useful civic-tech experience with responsible prototype boundaries. A public reporting platform would need verification, spam prevention, moderation, precise-location consent, privacy controls, and a secure shared backend. Rather than imply that unverified data were public facts, I labeled seeded reports as examples and kept new submissions local. I also focused on making expressive visuals without losing form clarity, mobile usability, or keyboard access.
Accomplishments
- Built a working end-to-end report flow with no account or API key.
- Added search and multi-dimensional filters to an accessible-minded reporting dashboard.
- Implemented browser-local report management and a clear option to remove local reports.
- Created a distinct responsive visual identity and an illustrative map interaction.
- Made the difference between implemented features and future plans explicit.
What I learned
Civic-tech prototypes need clear trust boundaries as much as polished design. Inclusive language, accessible controls, understandable statuses, and transparency around data are essential product features. A lightweight MVP can test the reporting experience before introducing sensitive backend workflows.
What's next
I would validate this concept with people with diverse access needs and local advocacy groups. Future releases could add consent-based accounts, secure moderation and verified public reports, real map data, partner-organization status updates, Arabic/English support, and independent accessibility testing.
Try the demo
To run the source locally, open index.html or serve the source folder with python3 -m http.server 8080 and visit http://localhost:8080. There are no dependencies, keys, or setup migrations.
Team
Samer Tallauze — product design and development.
Built With
- css3
- html5
- javascript
- vercel
