Ayesha Mazumdar's guest appearances

Ayesha Mazumdar

Hanselminutes with Scott Hanselman

The New Stack Podcast

Kelsey Hightower

Heather Terenzio

Cassidy Williams

Nicole Forsgren

Laura Frank

Camille Eddy

Joe Duffy

Erica Brescia

Lisette Sutherland

Stacy Kirk

Mark Rendle

Norm Judah

Roy Osherove

Ty Fujimura

Nicolas Steenhout

OwlTail

In this The New Stack Makers podcast, The New Stack Founder and Publisher Alex Williams spoke with Ayesha Mazumdar, senior UX designer at Optimizely, during Node+JS Interactive in Montreal about what needs to be done — and why human-centered designs are becoming not only nice-to-have features but technical requirements. Oftentimes, when developers and engineers think about human-centered design, there is a “very prominent tendency to go around designing for humans like us,” Mazumdar said. “This is subconsciously something I think we all fall victim to, but I think [human-centered design] is becoming this technical requirement,”  Mazumdar said. “We’re realizing certain users aren’t able to interact with the application we’ve built in certain ways, because we never accounted for that use case in the first place.” The main issue is that a design might be accessible for some people, but not necessarily for the end user, Mazumdar said. “Accessibility has to be continued down the line, and show up in the developers workflow so that we can ensure the final product is actually usable by absolutely everyone in all aspects,” Mazumdar said “And so I think, making it a technical requirement involves making it part of your development process,” including making it part of GitHub and Q&amp;A processes, for example. “Inserting accessibility checks along the way ensures that we don’t lose it at any point during the development cycle,” Mazumdar said.

In this The New Stack Makers podcast, The New Stack Founder and Publisher Alex Williams spoke with Ayesha Mazumdar, senior UX designer at Optimizely, during Node+JS Interactive in Montreal about what needs to be done — and why human-centered designs are becoming not only nice-to-have features but technical requirements. Oftentimes, when developers and engineers think about human-centered design, there is a “very prominent tendency to go around designing for humans like us,” Mazumdar said. “This is subconsciously something I think we all fall victim to, but I think [human-centered design] is becoming this technical requirement,” Mazumdar said. “We’re realizing certain users aren’t able to interact with the application we’ve built in certain ways, because we never accounted for that use case in the first place.” The main issue is that a design might be accessible for some people, but not necessarily for the end user, Mazumdar said. “Accessibility has to be continued down the line, and show up in the developers workflow so that we can ensure the final product is actually usable by absolutely everyone in all aspects,” Mazumdar said “And so I think, making it a technical requirement involves making it part of your development process,” including making it part of GitHub and Q&amp;A processes, for example. “Inserting accessibility checks along the way ensures that we don’t lose it at any point during the development cycle,” Mazumdar said.

Ayesha Mazumdar - Why Accessibility Is So Bad and How to Fix IT

Ayesha Mazumdar is a Senior UX Engineer at Optimizely and works to enable everyone to access the web no matter their ability. How does one build a culture at their company that values accessibility from the beginning? Where does a11y factor in when creating design systems, and later component libraries. How much ARIA is enough...or too much?Fable and Access Works both let you test your applications with people with disabilitiesCordelia Dillon's Accessibility Bake Off talkAn example of W3's Keyboard Interaction guidelines (link is specifically for Listbox)Ayesha's ReactBoston Scaling Accessibility video and slides

Ayesha Mazumdar is a Senior UX Engineer at Optimizely and works to enable everyone to access the web no matter their ability. How does one build a culture at their company that values accessibility from the beginning? Where does a11y factor in when creating design systems, and later component libraries. How much ARIA is enough...or too much?<ul><li><a href="https://www.makeitfable.com/" rel="nofollow" target="_blank">Fable</a> and <a href="https://access-works.com/" rel="nofollow" target="_blank">Access Works</a> both let you test your applications with people with disabilities</li><li><a href="https://conffab.com/video/the-great-accessibility-bake-off/" rel="nofollow" target="_blank">Cordelia Dillon's Accessibility Bake Off</a> talk</li><li>An example of <a href="https://www.w3.org/TR/wai-aria-practices/#Listbox" rel="nofollow" target="_blank">W3's Keyboard Interaction guidelines </a>(link is specifically for Listbox)</li><li>Ayesha's ReactBoston Scaling Accessibility <a href="https://www.youtube.com/watch?v=U1th3Qs-E_A&amp;feature=youtu.be" rel="nofollow" target="_blank">video</a> and <a href="https://slides.com/ayeshakmaz/scaling-a11y-react-boston" rel="nofollow" target="_blank">slides</a></li></ul>

Building a culture of accessibility from step zero with Ayesha Mazumdar