Mobile App Accessibility Roadmap
UA Mobile App Guild
This roadmap was developed in collaboration with the UA Mobile App Guild. If you are a mobile developer at Arizona, join our Slack channel #ua-mobile-dev for real-time support and monthly audit syncs.
Overview
This roadmap outlines how mobile app teams at Arizona can systematically improve accessibility. Whether you're building a new app or improving an existing one, follow these phases to ensure your app works for everyone and meets our legal requirements under ADA Title II.
Phase 1: Foundation (Weeks 1-4)
Goals
- Establish baseline accessibility audit
- Fix critical blockers that prevent access entirely
- Set up automated testing in CI/CD pipeline
Key actions
- Run accessibility scanner – Use Accessibility Inspector (iOS) or Accessibility Scanner (Android)
- Test with screen readers – VoiceOver (iOS) and TalkBack (Android)
- Fix missing labels – Ensure all interactive elements have accessible names
- Check touch targets – Minimum 44x44 points (iOS) or 48x48 dp (Android)
- Document current state – Create accessibility backlog with prioritized issues
Phase 2: Core compliance (Weeks 5-12)
Goals
- Achieve WCAG 2.1 Level AA for all core user flows
- Implement proper focus management
- Support Dynamic Type and display accommodations
Key actions
- Semantic structure – Use native components with proper roles and traits
- Color contrast – Minimum 4.5:1 for text, 3:1 for large text and UI components
- Dynamic Type support – Text scales from 100% to 235% without loss of functionality
- Focus order – Logical reading order that matches visual layout
- Error handling – Accessible error messages that identify the problem and solution
- Motion – Respect "Reduce Motion" system setting
Phase 3: Enhanced experience (Weeks 13-20)
Goals
- Go beyond compliance to create an excellent accessible experience
- Optimize for assistive technology power users
- Ensure feature parity for all users
Key actions
- Custom actions – Add rotor actions (iOS) or custom accessibility actions (Android) for complex interactions
- Live regions – Announce dynamic content changes appropriately
- Haptic feedback – Provide tactile confirmation for important actions
- Voice Control support – Ensure app works with voice commands
- Switch Control – Test and optimize for switch access users
Phase 4: Maintenance & culture (Ongoing)
Goals
- Prevent accessibility regressions
- Build accessibility into team culture
- Establish feedback channels with users
Key actions
- Automated testing – Run accessibility checks on every PR
- Manual testing sprints – Quarterly deep-dive testing with assistive technologies
- User testing – Include people with disabilities in usability studies
- Team training – Annual accessibility training for all developers
- Documentation – Maintain accessibility guidelines in your design system
Resources
- Mobile Accessibility Guide – Overview of mobile accessibility
- Apple Accessibility Developer Documentation
- Android Accessibility Developer Guide
- W3C Mobile Accessibility
- Testing Tools – Tools for accessibility testing
Need help?
Contact accessibility@arizona.edu for guidance on mobile app accessibility, audit support, or questions about this roadmap.