Accessibility vs latest Web APIs. Can’t we just get along?
summary
Argues that accessibility belongs in the core architecture and shows a working demo that uses the Web Speech API and device APIs to control Spotify playlists by voice, with grammars, RxJS streams and an abstract command factory; demo reliably recognizes commands in Chrome but browser support is limited and recognition runs server-side in Chrome only. Cites 119 million Europeans with hearing loss (2015) and Norway 450,000, and publishes code on GitHub requiring a Spotify key and Redis.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:14Mauricio Palma
- 22:20Kinds of Disabilities
- 25:12Web Speech Api
- 26:57Spotify Api
- 29:20Interim Result
- 35:45Methods that the Web Speech Recognition Offers
- 37:49Confidence Score
related talks
29mAccessibility vs latest Web APIs. Can’t we just get along?
38mAccessibility vs latest Web APIs. Can’t we just get along?
46mThe Sound of Silence: Web APIs for Accessibility for Visual and Hearing Impairments
51mIt's Spelled 'Accessibility', not 'Disability'
33mAccessibility and JS: side-by-side
29mProgramming for Accessibility
48mProgramming for accessibility
03mIt's spelled "accessibility," not "disability"