Summary
As we shift into a mobile first world, are you struggling to conceptualize and design accessible mobile experiences? While screen readers are included on both IOS and Android, it can be difficult and overwhelming for designers to learn about them. This session will help you get started! Samuel Proulx, Fable’s accessibility evangelist and a life-long screen reader user, will guide you through the ins and outs of screen readers on mobile. This interactive live demo will show you what an excellent mobile experience can sound like, give you some ideas of things to keep in mind during design, and help you make the case for bringing the voices of assistive technology users into the training and testing at your organization.
Key Insights
-
•
Mobile screen readers are built into both iOS and Android, needing no installation and can be activated via Siri or Google Assistant.
-
•
Android's accessibility ecosystem offers more customizability, including third-party screen readers and voices, but at the cost of greater complexity and inconsistency.
-
•
Apple’s VoiceOver is uniform across iOS devices, easier to learn, well-documented, and supported by a large user community, but less customizable.
-
•
Screen curtain on iOS allows blind users to protect their privacy by turning off the display while still using VoiceOver.
-
•
Most screen reader users do not keep default settings; they adjust voice, speech rate, and gestures to their individual needs.
-
•
Touchscreens provide spatial awareness for blind users, which is impossible with desktop screen readers relying on linear navigation.
-
•
Typing with a screen reader is a skill involving exploring keys by touch and double-tapping, which becomes muscle memory over time.
-
•
Blind users' choice between mobile platforms heavily depends on the screen reader experience rather than other device features.
-
•
Developers and designers can only test basic accessibility functionality on their own; true user experience requires research with native assistive tech users.
-
•
Accessibility efforts in Android started later than Apple’s, contributing to smaller community size and less documentation for Android screen readers.
Notable Quotes
"The screen reader is going to be the all-important all-consuming driver of why and how that decision gets made."
"If the built-in screen reader doesn’t meet your needs, you can go ahead and pick another screen reader on Android."
"Privacy for those of us who are blind and visually impaired is a big deal and we might not always realize when someone’s looking over our shoulder."
"You explore the keyboard with your finger until you find the letter that you are interested in and then you need to double tap on that letter."
"Disability is never one size fits all. The key to making accessibility is to offer customizability and to balance that with ease of use."
"Touch screens allowed blind people to use physical spatial information in a way that’s not possible on a desktop."
"Almost I can’t think of a single person who uses the out of the box configuration on a screen reader."
"Developers and designers testing products can determine what the screen reader reads, but they can’t determine the actual experience."
"The Android community tends to be smaller and less documented because their accessibility efforts started later than Apple’s."
"Apple just works, but if it doesn’t work for you, you’re probably not going to choose Apple."
Or choose a question:
More Videos
"Without shared organizational goals and customer-focused OKRs, democratization efforts fragment and fail to scale."
Jemma Ahmed Steve Carrod Chris Geison Dr. Shadi Janansefat Christopher NashDemocratization: Working with it, not against it [Advancing Research Community Workshop Series]
July 24, 2024
"It’s a constant balancing act wearing multiple hats like diplomat, facilitator, architect, and community manager."
Nina JurcicThe Design System Rollercoaster: From Enabler and Bottleneck to Catalyst for Change
October 3, 2023
"When you have a success, measure time saved and reduction in bugs to build your internal business case for the system."
Nathan Curtis Nalini P. Kotamraju Jack Moffett Dawn ResselDiscussion
June 9, 2016
"We had to be creative measuring accessibility success because we cannot detect screen reader use or certain disabilities directly."
Saara Kamppari-Miller Nicole Bergstrom Shashi JainKey Metrics: Comparing Three Letter Acronym Metrics That Include the Word “Key”
November 13, 2024
"Designing for change management is just as important as the product experience strategy."
Malini RaoLessons Learned from a 4-year Product Re-platforming Journey
June 9, 2021
"We are not collecting vanity analytics here, this data is doing real work informing design decisions."
Mackenzie Cockram Sara Branco Cunha Ian FranklinIntegrating Qualitative and Quantitative Research from Discovery to Live
December 16, 2022
"Day one of Design at Scale is going to be about ensuring craft on a massive scale."
Bria AlexanderOpening Remarks
June 9, 2021
"Growth boards enabled direction change sooner by objectively evaluating team health and strategic alignment."
Jackie HoLead Effectively While Preserving Team Autonomy with Growth Boards
January 8, 2024
"We need to relentlessly ask: technology is the answer, but what is the question?"
Dan HillDesigning for the infrastructures of everyday life
June 4, 2024