Accessibility as a First Class Citizen
summary
Demo shows a one‑screen React Native quest app with seven keys and a “set next key as found” button and uses the mac accessibility inspector (which is buggy) to prove the point. Core claim: four props — accessible, accessibilityLabel, accessibilityRole, accessibilityState — cover roughly 90–95% of mobile A11Y needs. Concrete actions: group children with accessible true, add labels for found/not found, set role to button, set state to disabled, and verify with the inspector.
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:50Who is accessibility for
- 6:17How to become more accessible
- 11:55Accessibility tooling
- 12:15Accessibility Inspector
- 13:00Accessibility Props
- 13:59Demo
- 15:57Accessibility Prop
- 18:04Accessibility Label
- 19:58Accessibility Role
- 21:43Accessibility State
related talks
20mBuilding apps for everyone - Accessibility with React Native
31mAccessibility for the App You're About to Ship
48mDevelopment for all the people
44mCrafting Great Accessible Experiences
32mReact native and accessibility
41mDemystifying Accessibility in React Apps
30mMake your React Native apps accessible
26mBe a React Native A11