WCAG 2.1 What's new and what to do with it
summary
WCAG 2.1 adds 17 new success criteria and targets mobile, low vision and cognitive gaps with specific fixes: require avoiding forced orientation, allow disabling single‑character keyboard shortcuts, provide non‑gesture controls for swipe actions and pointer cancellation, and ensure accessible name matches visible label for voice input. It mandates reflow to 320 CSS px, text spacing, non‑text contrast rules, autocomplete for forms, timeout warnings or saving, reduced‑motion support, status updates via aria‑live, and recommends 44×44 CSS px targets.
AI-written summary · about
chapters (36)
- 0:00Intro
- 3:27Web Platform standards
- 5:10Avoid a checklist mentality
- 5:39Define your accessibility approach early
- 6:05@ Goal: Continuous improvement
- 7:19Usability testing (with PwD)
- 8:13Testing with guidelines
- 9:00Automated testing
- 10:07Accessibility testing methods
- 10:53@ World Wide Web Consortium (W3C)
- 14:37What is a content guideline?
- 15:59WCAG 2.1: Principles, Guidelines, Success Criteria
- 16:43Levels: A, AA, AAA
- 17:47Structure of supporting info
- 18:32Understanding
- 18:58@ Why update WCAG?
- 19:39Text to GUI
- 20:01Buttons to touch screen
- 21:07WCAG 2.1 timescale
- 22:57Character Key Shortcuts
- 24:11Pointer Gestures
- 26:00Label in Name
- 27:04Motion Actuation
- 27:41Target Size (AAA)
- 29:15Reflow - 400% zoom
- 31:14Adaptable text
- 32:18Testing layouts and text spacing
- 35:00Non-text contrast
- 35:36User Interface Components (Interactive controls)
- 38:37Responsive page variations
- 38:59Content on Hover or Focus
- 40:33What's new - Cognitive
- 40:47Identify Input Purpose
- 41:05Autocomplete
- 41:55Timeouts
- 42:37Animations from interactions - Vestibular trigger!
