Discover 11 articles on Accessibility in mobile performance
Showing 11 of 11 articles (Page 1 of 1)
Slack's Android team tackled a VPAT accessibility audit and found critical gaps that affected screen reader users. Here's what they fixed and why it matters for your mobile app.
Nicolas Mayer Weiler from leboncoin shows why your 'accessible' Android component might still be failing users. Three stepper implementations, wildly different user experiences.
16% of the world's population has a disability. Yet most Flutter apps ship without basic accessibility features that could serve 1.3 billion people.
Swiggy tackled mobile web accessibility and discovered that following W3C guidelines was just the starting point. The real challenge? Making a food delivery app work seamlessly for screen reader users.
Swiggy made their food delivery app fully accessible for visually and physically challenged users. The result? A measurable increase in orders from users with disabilities.
Swiggy saw 5x growth in accessibility sessions after fixing one critical UX problem: their Android app treated screen reader users like robots, not humans.
Swiggy ignored accessibility for years, effectively locking out millions of users with disabilities. A Change.org petition changed everything.
React Native 0.65 just dropped with performance gains that'll make you rethink your mobile architecture. The Hermes engine upgrade alone is delivering 20-50% improvements on CPU-intensive workloads at Facebook.
Cash App's engineering team just open-sourced their solution to one of iOS development's most frustrating problems: testing accessibility without the manual grind.
Airbnb's Android app serves millions of travelers daily. But how many users were being left behind due to accessibility barriers?
Facebook's Ads Manager app demonstrates how React Native's Accessibility API makes mobile apps usable for everyone, including people with vision loss. Here's how they built it.