Accessibility (WCAG / ARIA) · 1 of 3
Question 1 of 3Navigation
Path 01 of 12
Frontend.
Client-side web development. 25 topics in alphabetical order, three questions each, answered from memory.
25 topics · 75 questions
01/25Frontend
Accessibility (WCAG / ARIA).
WCAG 2.2, ARIA patterns, keyboard navigation, screen readers, focus management, accessible forms and names.
What Accessibility (WCAG / ARIA) covers16 sub-skills
- 01WCAG 2.2 success criteria
- 02ARIA authoring patterns (W3C)
- 03Keyboard navigation & focus order
- 04Screen-reader semantics (NVDA/VoiceOver/JAWS)
- 05Color contrast & non-text contrast
- 06Focus management in SPAs & dialogs
- 07Accessible forms, labels, error messaging
- 08Accessible name & description computation
- 09Reduced-motion & vestibular safety
- 10Inclusive components (combobox, dialog, tabs, date picker)
- 11Cognitive accessibility (dyslexia, ADHD, plain language)
- 12Mobile a11y (touch targets, TalkBack, VoiceOver iOS, gestures)
- 13Accessibility testing (automated vs manual vs AT)
- 14Legal & compliance (ADA, 508, EN 301 549, lawsuits)
- 15Accessibility audits (WCAG-EM, VPAT/ACR craft)
- 16APCA & WCAG 3 (perceptual contrast, CSS Color 4)
Three of the 878 Accessibility (WCAG / ARIA) questions in the bank.