Accessibility vs latest Web APIs. Can’t we just get along?
summary
Argues that accessibility can be built with modern browser features and shows a working demo that ties Speech Recognition Web API to the Spotify Connect Web API using rxJS observables, speech grammar lists and confidence scores; audio is sent to a server engine so it’s online‑only and browser support is experimental (Edge incoming). Demonstrates handling ambiguous intents, multilingual BCP‑47 tags, and a flaky but functional prototype; cites 34.4 million European adults with disabling hearing impairment as motivation and publishes the code on GitHub.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:10Background
- 9:35Accessibility as the Core Concern
- 12:52Mac Dictation Keyboard Tool
- 14:31Speech Recognition
- 15:19Initial Configuration
- 16:28Grammar
- 16:53Observables
- 17:54Nlp
- 20:42Demo
- 27:32Browser Support
related talks
38mAccessibility 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'
33mAccessibility and JS: side-by-side
29mProgramming for Accessibility
48mProgramming for Accessibility