Find Elements By Accessibility Id
summary
Explains that Accessibility ID maps to platform APIs (Android UIAutomator, iOS XCUITest) and stays near-constant as UI depth increases while XPath requires Appium to serialize the view hierarchy to XML and run queries remotely, so it is slower — example: a simple demo finds a button in ~74 ms with accessibility id versus ~318 ms via XPath, and XPath timings explode with nesting (iOS crashes after ~50 nested views). Shows how to add IDs via contentDescription on Android and accessibilityLabel on iOS and notes frameworks (React Native, Flutter) and the 15% disability stat.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:05Overview
- 2:56What are accessibility IDs
- 4:43How accessibility IDs work
- 6:40How to add accessibility IDs
- 8:28iOS
- 9:04iOS Code
- 11:23Why is accessibility ID fast
- 11:54Simple app
- 12:22Speed test
- 12:55Accessibility
- 13:42Accessibility Statistics
- 14:46Accessibility Tests
- 15:58Conclusion
related talks
37mAndroid accessibility made easy
42mMake Your Mobile Apps Accessible to All
44mAccessibility Testing at Scale Powered by Appium
39mEasy Android Accessibility
40mAccessibility on Android in 2019
23mAccessibility as a First Class Citizen
43mAccessibility Made Simple
01h 01mAndroid for Everyone: Accessibility in Android