UX / UI / Accessibility

Re: Seed

An accessibility-focused receipt management concept designed for visually impaired users who need a clearer, more recoverable way to scan, store, and retrieve receipts.

Back to Work Discuss a project

Re: Seed mobile receipt accessibility mockup

Case Study

Designing receipt management around trust and recoverability.

Receipts are small, inconsistent, and easy to lose. For visually impaired users, that everyday task becomes an accessibility problem.

The Challenge

Users needed a way to scan, store, search, and understand receipts without relying on small visual details or fragile manual organization.

The Approach

We split the project into research, problem definition, ideation, wireframes, business planning, prototype design, and user testing.

Step 01Research

Step 02Define

Step 03Prototype

Step 04Test

Accessibility Direction

The design prioritized large visual separation between functions, simplified screens, voice-friendly retrieval, high-contrast modes, and explicit confirmation so users could trust where each receipt went.

The Outcome

The project showed that receipt management for visually impaired users is not only a contrast problem. It is a structure, confidence, and recoverability problem. The final prototype improved task clarity while exposing specific navigation and control patterns that still needed refinement.

Research focus

We clarified visual impairment as a broad target group that included myopia, glaucoma, blurred vision, and colour blindness. The primary product focus became users who experience blurred or low vision while trying to read, organize, and retrieve receipts.

Through interviews, we learned that some participants relied on enlarged fonts while others used voice reading tools. A recurring issue was that many apps did not visually separate functions clearly enough, making accurate tapping and retrieval difficult.

My role

I contributed to UX research, UI design, business planning, and prototype refinement. As the project developed, I also helped translate accessibility findings into interface decisions and supported the business plan around funding, subscription, and sustainability.

6Participants interviewed

4Users joined prototype testing

10Tasks tested in the prototype

2Light and dark interface modes

Research to Prototype

Accessibility became a structure problem, not just a contrast problem.

The strongest design moves came from making the flow simpler, the functional areas more distinct, and the recovery path clearer.

Re: Seed persona — **Persona**Research artifacts helped define the practical needs and emotional concerns of visually impaired users.

Re: Seed journey map — **Journey map**Mapping the receipt journey showed where uncertainty and recovery failures could happen.

Re: Seed user flow — **User flow**The flow focused on scanning, confirming, browsing history, and adjusting accessibility settings.

Re: Seed wireframes — **Wireframes**The early layout reduced visual clutter and separated core actions.

Re: Seed scan prototype animation — **Scan prototype**The scan experience needed feedback that felt immediate and reassuring.

Re: Seed history prototype animation — **History prototype**Receipt retrieval was designed as a predictable archive, not a hidden database.

Re: Seed light mode screens — **Light mode**Users could choose a brightness environment that felt comfortable for them.

Re: Seed dark mode screens — **Dark mode**The alternate theme supported lower-light conditions and reduced eye strain for some users.

Testing & Learning

The prototype worked best when each action had a clear place.

Testing showed that users appreciated the simple structure, but also revealed moments where common UI assumptions were not accessible enough.

What worked

Participants agreed that the color contrast was easier on the eyes, the functional separation was clear, and the simplified interface reduced mistaken taps.

What needed refinement

Some users did not immediately understand the filter button as a dropdown, and the top-right home button contradicted expected navigation habits.

What I learned

Accessibility became more concrete when I stopped thinking only about legibility and started thinking about confidence: how a user knows where they are, what happened, and how to recover if something goes wrong.

Next Case

Rooger Bookkeeper

A working macOS + iOS alpha exploring AI-assisted personal bookkeeping, quick capture, desktop review, budget management, and Notion-backed records.

View Rooger