LWCAdvancedaccessibilitywcaga11y
Build accessible LWCs meeting WCAG requirements
Real World Scenario
Enterprise procurement requires VPAT documentation but custom LWCs fail keyboard navigation and screen reader audits.
Expected Answer
• Use native lightning-base components inheriting platform accessibility
• Custom elements need aria-label, role, and keyboard handlers for Enter/Space
• Focus management on modal open/close trapping tab cycle
• Color contrast validation not relying on color alone for status
• Live regions aria-live for dynamic async updates
• Test with NVDA/VoiceOver and axe DevTools in CI
• Document accessibility ownership in component README
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Use native lightning-base components inheriting platform accessibility Also consider: Custom elements need aria-label, role, and keyboard handlers for Enter/Space In practice: Focus management on modal open/close trapping tab cycle Optimize for scale and operational observability.
Architect Perspective
Accessibility retrofits cost 5x—use base components and test a11y in definition of done.