
ALT Panel Discussion | Leveraging AI Tools for Accessibility in Product Development Session Chair: Lisette Arocha, CPWA, Accessibility and Inclusive Design Senior Manager, Products & Technology, PwC Panelists: David O’Neill, Technical Fellow, Vispero Jonathan Avila, CPWA, Chief Accessibility Officer, Level Access Michael Cooper, Web Accessibility Technical Strategist Ed Summers, Head of Accessibility, GitHub

ALT Panel Discussion | Leveraging AI Tools for Accessibility in Product Development Session Chair: Lisette Arocha, CPWA, Accessibility and Inclusive Design Senior Manager, Products & Technology, PwC Panelists: David O’Neill, Technical Fellow, Vispero Jonathan Avila, CPWA, Chief Accessibility Officer, Level Access Michael Cooper, Web Accessibility Technical Strategist Ed Summers, Head of Accessibility, GitHub

ALT Panel Discussion | New Imperatives for Kiosks and Self-Service Payment Systems Session Chair: Matt Ater, Vice President, TPGi, A Vispero Company Panelists: Rick Smith, Director, Business Development, Elo Touch Solutions Marshall Law, Co-Founder and Business Development, Rivalry Tech Peter Jarvis, Senior Executive VP, Storm Interface Clark Rachfal, Director of Advocacy and Governmental Affairs, American Council of the Blind (ACB)

ALT Flow chart for determining when :focus-visible applies. Asks four questions - 1. Has the user expressed a preference for always visible focus? If yes, :focus-visible applies. If no, go to next question. 2. Does the focused element support keyboard input? If yes, :focus-visible applies. If no, go to next question. 3. Is the user interacting with the focused element with a non-pointing device? If yes, :focus-visible applies. If no, go to next question. 4. Did a script cause focus to move from a previously visibly-focused element? If yes, :focus-visible applies. If no, :focus-visible does not apply























