Arizona Digital and partner units build mobile apps that must meet Title II’s WCAG 2.1/2.2 AA requirements.
Title II mobile deadline: April 24, 2026
What this page helps you do
- Align your mobile app roadmap with Title II timelines and WCAG 2.2 AA requirements.
- Coordinate patterns and testing between mobile apps and the Web & Apps hub.
- Plan VoiceOver/TalkBack testing and know when to ask for help from Accessibility and Arizona Digital.
Top tasks
| Task | Steps | Primary Tools |
|---|---|---|
| Inventory apps | List platforms, owners, frameworks, usage; log in roadmap. | Mobile Roadmap tracker |
| Design accessible patterns | Map tokens to platform APIs → ensure focus order → provide large text assets. | iOS Human Interface Guidelines, Material Design |
| Audit & remediate | Run VoiceOver/TalkBack tests → log defects → integrate fixes into sprints. | Xcode Accessibility Inspector, Android Accessibility Scanner |
Impactful principles & tools
Keep the mobile backlog lean by aligning with the WCAG 2.2 AA highlights and automating checks.
- Meet SC 2.4.11 and 2.5.8 by ensuring focus indicators remain visible and touch targets hit 44x44 px (iOS) or 48x48 dp (Android).
- Provide single-tap alternatives to drag gestures (SC 2.5.7) and support external keyboards.
- Use Accessibility Insights for Android/iOS to scan views during development.
- Validate companion web workflows with WAVE and DubBot so embedded content matches app behavior.
- Document VoiceOver/TalkBack passes alongside automated linting in CI.
Release notes, support docs, and store screenshots must follow content accessibility rules:
- Run Microsoft Accessibility Checker on Word/PowerPoint instructions prior to PDF export.
- Use Adobe PDF remediation for onboarding packets (reading order, labels, tags).
- Provide descriptive alt text for App Store / Play Store screenshots following WebAIM guidance.
Guidance
Follow the mobile roadmap to hit Title II milestones. Prioritize student services, financial aid, and campus safety apps.
- Respect Dynamic Type, Bold Text, High Contrast, Reduce Motion, and system color schemes.
- Ensure tappable targets ≥ 44x44 px with clear focus indicators.
- Automated lint rules for labels, contrast, and large text.
- Manual screen-reader sweeps with VoiceOver (iOS) and TalkBack (Android) every sprint.
- Quarterly regression with JAWS/NVDA for companion web flows.
Tools & contacts
Assistive technologies to test with
Mobile releases must document test passes with:
- VoiceOver (iOS/iPadOS) – gestures, rotor navigation, focus order.
- TalkBack (Android) – swipe navigation, custom actions, announcements.
- JAWS/ NVDA when apps embed web content or rely on companion sites.
- Fusion / ZoomText for Windows management consoles or kiosk mirroring.
Reference Assistive Technology Coverage for expectations and training.
Training & community
- Mobile App Guild office hours (bi-weekly).
- VoiceOver/TalkBack testing labs (monthly).
- Title II readiness briefings for app owners.
Feedback
Email accessibility@arizona.edu with app release plans or blockers. Last reviewed: 2026-01-05.
Next steps for mobile app owners
- This month: Complete the inventory in the mobile roadmap and identify your top two student- or public-facing apps.
- This quarter: Run VoiceOver and TalkBack tests on priority flows and log issues using the WCAG 2.2 checklist in the Web & Apps hub.
- Before April 2026: Ensure every supported app has an accessibility statement, documented test coverage, and a plan for exceptions or alternative access.
Use the Support & Consultations page if you need help planning audits, user testing, or vendor coordination.
Related guides you may need
Your work may overlap with these roles: