Accessibility panel
summary
Discussion gives concrete takeaways: build an agent harness around LLMs and do manual reviews so generated UIs do not introduce flashing or inaccessible controls; prefer invisible, behavior-based checks like reCAPTCHA risk-based approach over memory CAPTCHAs; consult OWASP LLM Top 10 for security risks and prompt‑injection defenses; measure impact with screen‑reader tests, accessibility testing tools, SEO signals and cost estimates so managers see measurable wins and legal risk reduction.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:07AI UI aesthetics
- 3:15Music preferences
- 4:40Trusting AI agents
- 5:21Accessible CAPTCHA alternatives
- 6:26AI safety approach
- 8:55AI agents in web ads
- 11:00Convincing management
- 12:26Closing
related talks
46mGuerilla Accessibility Testing Techniques
41mAccessibility is a Requirement
59mAccessibility in UX: A panel discussion
26mDon't Develop Just for Yourself - A Developer's Checklist to Accessibility
26mHow (Not) to Fail at Accessibility
01h 05mAccessibility Testing 101
45mTips from the Trenches: Accessibility Testing
25mSecurity and Accessibility can be friends!
