A city transit team plans a mobile application that shows routes, arrival times, and service changes. The first prototype looks polished, but testing reveals that appearance alone does not make the tool usable. A passenger with limited vision cannot read pale text against the map. Another user relies on a screen reader and hears station names in a confusing order. A traveler with reduced movement needs to know whether elevators are working before leaving home. The team replaces assumptions with structured interviews and practical trials. Designers increase contrast, provide scalable text, label every interactive control, and ensure that essential information remains available without color. Engineers connect elevator status to the same update system used for delays. They also create a low-data mode for passengers with unreliable connections. Each change is tested on several devices and with keyboard navigation, voice tools, and enlarged displays. The group publishes a clear way to report problems and records which accessibility standards each release meets. Not every request can be completed immediately, so the roadmap explains priorities instead of hiding limitations. The finished application is better for many people, including visitors carrying luggage or reading a screen in bright sunlight. Accessible design is not an optional layer added at the end. It is a method of understanding varied users from the beginning.