Accessibility as an architecture concern: semantic HTML first, keyboard and focus management, ARIA used correctly, accessible design-system components, automated and manual testing, and making it stick across teams.
About 1 in 6 people worldwide live with a significant disability (WHO). Add temporary and situational impairments (a broken arm, bright sunlight, a noisy train) and accessibility affects everyone at some point. It's also a legal requirement in many markets: the ADA in the US, the European Accessibility Act (in force from June 2025), and EN 301 549 for public sector procurement, all referencing WCAG 2.x AA.
Why it belongs to architects rather than individual developers:
Dialog, Menu, and Combobox are accessible, thousands of usages are. If they're not, no individual team can fix it.The four WCAG principles (POUR): content must be Perceivable (alt text, captions, contrast), Operable (keyboard, enough time, no seizure triggers), Understandable (clear labels, predictable behavior, helpful errors), and Robust (works with assistive technologies, valid semantics).