Intro to Blazing Web Accessibility (*)
summary
A concrete build shows a Blazor site wired to Microsoft Cognitive Services to add paragraph-by-paragraph TTS that reads specific DOM elements instead of full screen reader linearized output. Implementation uses a tiny JavaScript interop shim, a C# speech service calling the Speech SDK (or REST for WASM), and Azure keys; the demo runs end-to-end as a proof‑of‑concept but flags cost and hosting tradeoffs for production. Expect working code on GitHub and step‑by‑step setup for Blazor + Azure Cognitive Speech.
AI-written summary · about
chapters (11)
- 0:00Welcome and introduction
- 1:28Talk overview and speaker intro
- 2:54Accessibility basics and inclusion
- 8:20Disabilities and accessibility needs
- 13:42Screen readers vs text-to-speech
- 14:03Blazor basics and setup
- 17:56Microsoft Cognitive Services overview
- 20:08Future of web accessibility demo
- 24:09Step-by-step implementation guide
- 39:46Summary and closing remarks
- 40:29Q&A session
related talks
56mBlazing Accessibility Basics
01h 00mASP.NET Blazor programming 101
48mProgramming for Accessibility
17mBuild an AI-powered content composer in Blazor
01h 02mBlazor in more depth
56mModern Web UI with Blazor WebAssembly
01h 01mBlazor, a new framework for browser-based .NET apps
29mAccessibility vs latest Web APIs. Can’t we just get along?
