Auditing your App with the Accessibility Inspector
summary
Opens Xcode’s Accessibility Inspector and runs the audit against a simulator to list concrete failures: many “hit area is too small” warnings (25×25 → change constraints to 44×44), bad labels like “bird icon” (set accessibilityLabel to “tweet”), and text that ignores Dynamic Type. Fixes use preferredFont(for:) or UIFontMetrics.scaledFont(for:), set adjustsFontForContentSizeCategory, and update layout in traitCollectionDidChange (switch stack view axis). Re-run audit; warnings clear and VoiceOver preview reads the corrected labels.
AI-written summary · about
chapters (10)
- 0:00Introduction to accessibility
- 1:50Why accessibility matters
- 3:31Discovering the inspector
- 7:27Accessibility inspector tool
- 8:30Auditing app accessibility
- 12:40Fixing hit area issues
- 16:58Improving accessibility labels
- 18:51Implementing dynamic text
- 23:35Adaptive layouts for large text
- 25:26Final audit and conclusion
related talks
36mFrom Zero to Accessible in 30 minutes
48mDevelopment for all the people
40mIncreasing Your App's Accessibility to Optimize It for All Users
31mAccessibility for the App You're About to Ship
27mHow I Learned to Stop Worrying and Love Voiceover
29mInclusive and Accessible App Development
29mUnlocking Inclusion, How to Get Started With A11y Testing
40mGetting started with mobile accessibility: iOS, Android, and Flutter