D-01 · US nonprofit community app case study
A community organisation serving families needs an app that every member can use, including those who rely on screen readers.
The short answer
AiS LABZ is building a US nonprofit a cross-platform mobile app for iOS and Android: news, events with ticketing and QR check-in, donations, push notifications and a member directory, run from an admin portal. It is designed and tested to WCAG 2.2 AA, with VoiceOver and TalkBack support, over a 12 to 14 week build.
What was in the way?
- Updates, events and giving lived in separate places.
- Members relying on assistive technology needed an experience built for them, not retrofitted.
What changed?
- Scope agreed: 8 core modules from sign-in to donations.
- Four delivery milestones: kickoff, backend and staging, QA and accessibility, store submission and handover.
- Client ownership contracted: repository, cloud environment and both app store accounts.
How did we do it?
The same four-phase method on every engagement: diagnose, model, build, compound.
Diagnose
Discovery with the organisation's team: audiences, events, giving and the existing WordPress data.
Model
One app, three jobs: stay informed, show up, give. Accessibility treated as a launch requirement, not a feature.
Build
Flutter app for iOS and Android, an Angular admin portal, a .NET 9 API, and a MySQL layer that syncs with the existing WordPress site, hosted in the client's own cloud.
Compound
A 90-day post-launch support window, then a roadmap for volunteers, fundraising tracking and learning resources.
Who did we work with?
What happens next?
Backend and staging delivery, with iOS and Android test builds, then accessibility QA.
Common questions
Because retrofitting screen-reader support is slower and worse. WCAG 2.2 AA, VoiceOver and TalkBack are tested before launch, not after.
The organisation does: the code, the cloud environment and both app store accounts.
Yes. The admin portal manages news, events, banners, campaigns and push notifications.
Your number next