Accessibility is engineering, not a checklist

Retrofitting accessibility is expensive. Building it into the component layer costs almost nothing.

Fix it once, in the primitives Keyboard handling, focus management, roles and labels belong in your button, dialog, menu and form primitives. Product engineers should get correct behaviour by default.

What scanners miss - Focus order that makes no sense - Announcements that never fire on dynamic updates - Motion that triggers vestibular symptoms - Colour used as the only carrier of meaning

Test the way people use it Keyboard-only pass on every new flow. A screen reader pass on the critical path. Both take minutes once they are a habit.

The business case is real Accessible products are more usable for everyone, rank better in search, and keep procurement and regulatory conversations short.