Conversations around web accessibility
Interviews with people involved in one way or another with web accessibility.
In which Liz Jackson tells us she wishes people viewed accessibility as an opportunity to engage, rather than a legal compliance thing.
Liz Jackson says it’s not enough to fix accessibility, people with disabilities must be included. She says: “I think somebody thinks that if they just smooth something out and they make it usable that we won’t have feelings about it. But, we are a people that probably hungers for choice, right? Like, we want to have opinions about things. We want to be delighted. So to simply try and smooth something out and endeavor no further, I think is… we’re missing something.”
Amy Carney tells us accessibility is not just a checklist of standards but that we really are building experience for people and allowing them to open up opportunities.
Amy Carney tells us that accessibility “comes down to a design perspective. We’re designing to include people, specifically people with disabilities. And that is based on enabling people with disabilities to access content and web applications online.”
Alli says that getting the right people in the same room at the start of a project is very difficult and can impede accessibility.
Alli tells us how experiencing lack of accessibility for a classmate of hers in the built environment helped her understand the importance of accessibility on the web.
Jen tells us to start accessibility today, to start with one thing. Then to do one more thing, and then one more.
Jen Luker tells us, among other things, that with thoroughness comes confusion – if you’re trying to learn all of WCAG and ARIA at once, you’ll get overwhelmed
Chris tells us “the biggest challenge that [the accessibility community is] going to have, and it currently stands now, is the never-ending library framework”
Chris is a front-end developer based in Detroit, MI. He tells us, among other things, that learning about accessibility is an ongoing process.
