Blazing Accessibility Basics
summary
Blazor sites that follow WCAG use semantic HTML, keyboardable controls, and alt text stored in models to serve the world’s ~1B people with disabilities. Demonstrates using Accessibility Insights (Edge/Chrome plugin plus CI/CD integrations) to run automated checks and guided assessments, enforcing POUR principles and letting builds fail. Covers practical fixes: add footer nav when Bootstrap menus vanish at 400 percent zoom, use data‑annotations for validation, provide timer‑extend buttons, and prefer clear headings and readable fonts.
AI-written summary · about
chapters (18)
- 0:00Start
- 0:25Introduction
- 2:34Inclusive Design
- 3:34Personal Spectrum
- 5:17Web Content Accessibility Guidelines
- 11:39Perceivable Operable Understandable and Robust
- 15:45Color Blindness
- 16:48Standard Bootstrap Templates
- 17:31Images Are Resizable
- 18:18Structure of the Application
- 23:04Navigation
- 28:35Avoid Timers
- 35:10Page Component
- 35:23Comment Form
- 42:32Add a New Component
- 48:28Footer Item
- 49:20Accessibility Scanner
- 52:17How Can You Use Screen Reader and Windows Testing on Websites
related talks
46mIntro to Blazing Web Accessibility (*)
22mWeb Accessibility - a better user experience for everyone!
01h 07mA web for anyone, anywhere, anytime
35mAccelerating accessibility in web
37mAccessibility Matters: Creating a Better Web
45mA Web for Anyone, Anywhere, Anytime
01h 05mAccessibility Testing 101
15mRapid Introduction to Web Accessibility