I build Mobile AppsNew

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 theWeb & Apps hub.
• Plan VoiceOver/TalkBack testing and know when to ask for help from Accessibility and Arizona Digital.

Top tasks

Impactful principles & tools

Keep the mobile backlog lean by aligning with theWCAG 2.2 AA highlightsand automating checks.

Focus, targets, and gestures

• 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.

Testing & monitoring stack

• 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.

Docs, PDFs, and store listings

Release notes, support docs, and store screenshots must follow content accessibility rules:

• Run Microsoft Accessibility Checker on Word/PowerPoint instructions prior to PDF export.
• UseAdobe PDF remediationfor onboarding packets (reading order, labels, tags).
• Provide descriptive alt text for App Store / Play Store screenshots followingWebAIM guidance.

Guidance

Roadmap alignment

Follow themobile roadmapto hit Title II milestones. Prioritize student services, financial aid, and campus safety apps.

Design system integration

• Respect Dynamic Type, Bold Text, High Contrast, Reduce Motion, and system color schemes.
• Ensure tappable targets 44x44 px with clear focus indicators.

Testing cadence

1. Automated lint rules for labels, contrast, and large text.
2. Manual screen-reader sweeps with VoiceOver (iOS) and TalkBack (Android) every sprint.
3. 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/NVDAwhen apps embed web content or rely on companion sites.
• Fusion/ZoomTextfor Windows management consoles or kiosk mirroring.

ReferenceAssistive Technology Coveragefor 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

Emailaccessibility@arizona.eduwith app release plans or blockers. Last reviewed: 2026-01-05.

Next steps for mobile app owners

• This month:Complete the inventory in themobile roadmapand identify your top two student- or public-facing apps.
• This quarter:Run VoiceOver and TalkBack tests on priority flows and log issues using theWCAG 2.2 checklistin 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 theSupport & Consultationspage if you need help planning audits, user testing, or vendor coordination.

Related guides you may need

Your work may overlap with these roles: