How can we avoid only testing for and addressing accessibility in QA? How can we incorporate accessibility compliance earlier in the process? What tools would help us along the way?
I would like to discuss how developers can be accessibility champions and incorporate best practices into the development process. I will have examples to share of easy wins, common things to check for in code reviews, and some more elaborate examples of accessible UI development patterns if we want to look at them. I'm hoping for a great conversation and ideas from the community as well.
Christina Adams is a Certified Professional in Web Accessibility from the International Association of Accessibility Professionals (IAAP). She is a Digital Accessibility Software Engineer for Siteimprove working on global accessibility initiatives and providing accessible solutions for our customer's digital assets. Her goal is to champion inclusive design and development practices for equitable digital spaces.