HomeArticlesDesigning for Accessibility (Google I/O’19) Designing for Accessibility (Google I/O’19) By Eric Benedict November 15, 2019 Articles, Blog 1 Comment Tags:design thinking, developer news, developers, Elise Roy, Elise Roy Story, Google, google 2019, Google I/O, Google I/O 2019, Google IO, google io updates, google livestream, human rights lawyer, I/O, IO, io 19, io announcements, io19 Related Posts Interaction Design and Tasks | UX/UI Design | Product Design | Udacity How to draw M416 Gun from PUBG I Tried to Draw My Dog… About Author admin One Comment Grayson Peddie May 17, 2019 Google Developers, how can I help correct the closed caption when I see "hearing laugh" and "hearing lapse?" I think she said "hearing loss." It seems the automatic closed captioning is not picking up the "ss" sound when she says "hearing loss." 4:03 "Disability encompasses ah of us" should be "Disability encompasses all of us." Seems to me the automatic closed caption thinks she said "ah" instead of "all." 4:15 For confirmation, did she say "yeah" in "who yeah has broken their legs or arms?" 6:26 "From na2 design." I don't know if I was lipreading right, but didn't she say "from my to design?" Could automatic closed captioning system do lipreading in the future? 7:20 Again, I did some more lipreading and I think she said "it allowed me to celebrate" and the dynamics of her voice caused automatic closed caption to miss "me" after "allowed" as in "it allowed to celebrate." 7:58 "So this is Dimitri connects key" should be "So this is Dimitri Kanevsky." 20:57 "Start with one invent for money" should be "start with one invent for many." At least she said "start with one, invent for many" the second time and automatic closed caption got it right. Reply Add a Comment Cancel reply Your email address will not be published. Required fields are marked *Comment:*Name:* Email Address:* Save my name, email, and website in this browser for the next time I comment.