Accessibility vs latest Web APIs. Can’t we just get along?
summary
Argues that accessibility and modern Web APIs can coexist, demonstrates a Spotify Connect demo driven by the Web Speech API using grammars and confidence scores to map intents to actions, proposes using device sensors like ambient light and other APIs to adapt contrast, cites ~190 million Europeans with hearing loss as motivation, reports the speech engine is Chrome‑only and server‑side, and shows the prototype mostly works though accuracy and browser support limit roll‑out.
AI-written summary · about
chapters (10)
- 0:00Start
- 20:53WEB SPEECH API
- 22:34Involves a server based recognition engine
- 23:05The SpeechRecognition controller
- 24:20new SpeechGrammarList()
- 27:39Intents
- 29:34start()
- 30:18onerror
- 35:16Browser Support
- 36:34TRY IT OUT!
related talks
29mAccessibility vs latest Web APIs. Can’t we just get along?
46mAccessibility vs latest Web APIs. Can’t we just get along?
46mThe Sound of Silence: Web APIs for Accessibility for Visual and Hearing Impairments
01h 07mA web for anyone, anywhere, anytime
51mIt's Spelled 'Accessibility', not 'Disability'
48mProgramming for accessibility
40mAccessibility: What If We Let Users Customize ...
23mWarm-Up Talk: Browser APIs – the unknown Super Heroes