4 ms·
As someone who built many UIs at Google, the reason it works is because Google's UX teams take accessibility very seriously. At the OS level especially. As an
by calderwoodra 3y ago
As someone who built many UIs at Google, the reason it works is because Google's UX teams take accessibility very seriously. At the OS level especially.
As an anecdote, I was upgrading some outdated code for the dialpad in the phone app and we worked closely with some blind Googlers to understand how they place calls and make sure we weren't breaking it for them. Really interesting stuff.
- devinprater 3y agoOh wow, that is really nice. I love how stable Android, and Android accessibility, is. No speech engine crashing while feeling around the home screen for no reason, Braille input (for the displays that are supported grumble grumble), is fast and clean and never slows down after like 20 words. Still trying to get into the TalkBack beta program though, since they're probably testing support for the display I own now. But anyway, thank you so much for working on this. Now if only Youtube supported accessibility actions instead of having buttons everywhere on each video widget in the list of videos.