I really liked the case study app presented in this talk! I'm curious to know if you have recommendations around how to "think" with accessibility in mind. Something that I have noticed in all the companies/products that I have worked on is that we often realize later on that our app isn't accessible, and then we realize we should have been thinking about accessibility from the very beginning, rather than as an afterthought. Do you have any ideas on how to change the way you approach building something so that accessibility is part of the building process (rather than an afterthought)?
Miranda is a technical writer and product lead at VMware as well as founder of Books on Code, which is a platform for programmers who love to learn through technical books.
Location
San Francisco, CA
Education
MA English Literature
Work
Senior Technical Writer at VMware (previously Pivotal)
Hi Vaidehi! So cool seeing your comment. I've been following your Tweets through my booksoncode handle.
I honestly think it's helpful to think about your site through access needs. So, try accessing your web app using only a keyboard, or using keyboard paired with screenreader, paired with voice commands or with other assistive technologies.
There's also a book I highly recommend, Practical Web Inclusion and Accessibility, which is organized into different groups of users and their access needs. I think taking a user-centric approach is important.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I really liked the case study app presented in this talk! I'm curious to know if you have recommendations around how to "think" with accessibility in mind. Something that I have noticed in all the companies/products that I have worked on is that we often realize later on that our app isn't accessible, and then we realize we should have been thinking about accessibility from the very beginning, rather than as an afterthought. Do you have any ideas on how to change the way you approach building something so that accessibility is part of the building process (rather than an afterthought)?
Hi Vaidehi! So cool seeing your comment. I've been following your Tweets through my booksoncode handle.
I honestly think it's helpful to think about your site through access needs. So, try accessing your web app using only a keyboard, or using keyboard paired with screenreader, paired with voice commands or with other assistive technologies.
There's also a book I highly recommend, Practical Web Inclusion and Accessibility, which is organized into different groups of users and their access needs. I think taking a user-centric approach is important.