Peculiarities of Web Interfaces When Working with a Screen Reader
summary
Yandex adopted WCAG 2.0, created an internal accessibility guide, and ran user research with blind and low-vision people using screen readers and braille displays. They added semantic HTML, ARIA attributes, alt and title on images, and full keyboard workflows (notably in Yandex.Images and Mail), which reduced reply time in the light Mail from ~56s to 20–23s and, with a partial rollout on Gosuslugi, increased active users from 1.2M to nearly 6M; early accessibility work cost about 10% versus up to 30% if done later.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 3:06How screen readers work
- 6:19Accessibility audience size
- 7:45WCAG standard benefits
- 9:10Government portal case study
- 13:32Yandex Pictures improvements
- 16:47Yandex Mail versions
- 20:50Facebook accessibility
- 23:44Business benefits
- 25:09Internal accessibility practices
- 27:18Implementing accessibility
- 30:08Key techniques
- 30:53Digital inclusion responsibility
related talks
29mAccessibility Matters: Creating a Better Web
31mBringing the Web Back to the Blind
44mWeb accessibility for Artisans
46mExclusive design
22mWeb Accessibility - a better user experience for everyone!
01h 07mA web for anyone, anywhere, anytime
45mA Web for Anyone, Anywhere, Anytime
01h 00mWorkshop: Improving Marketplace Accessibility for the Blind, from the Market’s Experience (Part 1)