10 UX Mistakes for Blind Users
summary
Talk examines ten real UX mistakes that make web interfaces inaccessible to blind users, using examples from Yandex Market. It covers issues like excessive headings, wrong ARIA roles, incorrect reading order, fragmented elements and text, hidden important content, nonfunctional button markup, and semantic tags (em/b) not affecting screen-reader intonation, and presents React-based solutions and best practices for mid/senior interface developers.
AI-written summary · about
chapters (18)
- 0:00Small talk
- 2:46Introduction
- 6:41Mistake 1. Overusing headings
- 11:44Mistake 2. Redundant roles
- 14:17Mistake 3. Incorrect reading order
- 17:15Mistake 4. Split element
- 19:02Mistake 5. Split text
- 21:04Mistake 6. Not hiding unnecessary internals
- 22:29Mistake 7. Hiding interactive internals
- 23:48Mistake 8. Losing context in captions
- 24:58Mistake 9. Overly logical list
- 26:32Mistake 10. Poorly designed navigation
- 29:04Conclusion
- 30:28Question 1 (from expert). What drives such deep dive into a11y?
- 33:24Question 2. Why not just aria-label?
- 38:02Question 3. How many mistakes were left out?
- 38:29Question 4. Have neural networks improved content reading for the blind?
- 42:19Moving on to discussion
related talks
22mInclusive UI design
56mAccessibility for UX: Don't worry, it's much worse than you think
11mOne Blind Weekend
41mTales of Accessibility Failures
46mYou Can Come to This Talk with Your Eyes Closed
43mTalk To Me - Making web sites accessible
43mThe User Experience of a Blind Person
59mAccessibility in UX: A panel discussion