Creating Inclusive Apps with React Native • Larene Le Gassick • YOW! 2017

Building accessibility into apps benefits all users, not just those with disabilities - known as the “curb cut effect” where accessibility features end up helping everyone

Mobile apps need different accessibility considerations compared to desktop due to:

• Varying lighting conditions and outdoor use
• One-handed operation while multitasking
• Smaller screen sizes
• Variable network conditions
• Battery life constraints

React Native makes accessibility implementation relatively straightforward through built-in properties:

• accessible={true/false}
• accessibilityLabel
• accessibilityTraits

Key tools for testing accessibility:

• iOS VoiceOver
• Android TalkBack
• Accessibility Inspector on Mac
• Android Accessibility Scanner

Build accessibility into team culture through:

• Increasing awareness across all team members
• Including accessibility requirements in user stories
• Regular accessibility testing during development
• Not relying on a single “accessibility person”

The “next billion” internet users will primarily access via mobile devices with:

• 4-inch screens
• Limited RAM (< 512MB)
• Spotty internet connections
• Flight mode usage to conserve data/battery

Accessibility should be considered from project start, not retrofitted later

Components need to be:

• Perceivable
• Understandable
• Robust
• Have sufficient touch targets
• Maintain proper navigation order

Different OS platforms may require different accessibility implementations - develop for Android first as it tends to have more accessibility issues

Regular testing with actual users and assistive technologies is crucial for proper implementation