AccessAble
Where accessibility meets community
01. Project Objective
AccessAble was designed to help people with disabilities and their caregivers plan outings without stress. Our goal was to build a reliable source of accessibility information powered by community reviews, easy enough to use on both mobile and web.
02. Research
Market Insights
Competitor Analysis
-
27% of Canadians 15+ live with a disability.
​
-
56% face barriers in physical spaces, 17% face online barriers.
​
-
Global accessibility tech market projected to exceed $25B.
-
Narrow focus on one type of disability.
​
-
Limited filtering and personalization.
​
-
Few AI features to speed up review reading.
​
-
Minimal use of media to prove real accessibility.
03. Ideation
After mapping user needs and market gaps, we moved into ideation. We explored how to make accessibility information both simple and trustworthy.
Starting with sketches and mobile-first user flows, we shaped quick on-the-go searches. Later, we extended ideas to web, giving users larger-screen support for planning at home.
04. Solution
Accessibility info today is broken. It is scattered, incomplete, and focused on only one disability type.
​
AccessAble fills this gap. It brings reviews, photos, and AI summaries into one place. The platform helps people plan with ease and see real proof before they go out.
Built with Purpose
AccessAble was not made to be another tool. It was made to stand for trust, dignity, and freedom of choice.
​
The mission is simple: give people control of their own journeys. Every review, every photo, every voice adds to a system built on truth, not guesswork.​
06. Wireframing
We began with mobile. Most users plan outings on their phones, so starting small was the best way to test flows. We later moved to web, making the platform easy to use for both mobile and desktop users.
Mid-fi
Our mid-fi wireframes shaped the product. They tested key flows like search, review, and map filters. From there, we refined the layout for clarity and added accessibility features early. This made both mobile and web consistent and inclusive.
After we gathered feedback, and refined our research. We moved into high-fidelity design to bring it alive.
07. Prototyping
Prototyping helped us see what worked, what felt confusing, and how real users with disabilities could move through the app. Each iteration tied back to the research, showing how our design choices solved real barriers.
Version 1 - Initial Prototype
The first version showed the idea but had problems. The text was hard to read because it blended with the background. Elements were not consistent. This made it harder to use.
Testing & Feedback
We learned the problems after many usability tests. Some tests were with people who had visual and cognitive challenges. We also shared the prototype with 30 people from the industry. Their feedback confirmed the issues.
Version 2 - Improved Prototype
We improved the final version with stronger contrast, better spacing, and a cleaner layout.
All updates followed WCAG 2.2 accessibility standards to make it easy to read, simple to use, and aligned with the mobile app.
08. Web Version
After testing the mobile app, we brought AccessAble to the web. This expansion gave the platform more reach and proved it could adapt to different needs and screens.
08. Outcome
Next Steps
The MVP showed clear demand. The next step is to grow fast and smart. We plan to secure CA$150K in pre-seed funding to support marketing, mobile-native development, and code migration. Within 12 months, the goal is to onboard 100 paying venues and partner with at least 3 cities.
Reflections
AccessAble proved that design can remove barriers when inclusivity comes first. Testing with people who have visual and cognitive disabilities showed how much clarity and contrast matter.
Every change made the app easier to use. Following WCAG 2.2 standards reminded us that accessibility is not optional. It is the core of good design.
