Interactive interfaces often introduce accessibility barriers when dynamic visual feedback fails to translate to assistive technologies like screen readers or keyboard navigation.
1. Full keyboard operability and visible focus
Every interactive component—buttons, dropdowns, modal triggers, sliders, accordions—must be fully operable using standard keys (Tab, Shift+Tab, Enter, Space, Arrow keys, Esc).
Never remove the browser's default focus indicator with `outline: none` unless you provide a custom, high-contrast focus ring (WCAG 2.2 requires a minimum 3:1 contrast ratio against adjacent colors).
2. Meaningful ARIA states for dynamic components
When a visual component opens, expands, or enters an error state, screen-reader users must be informed programmatically:
- **Accordions & Menus:** Use `aria-expanded="true|false"` and `aria-controls="panel-id"`.
- **Tabs:** Use `role="tablist"`, `role="tab"`, and `aria-selected="true|false"`.
- **Modals & Dialogs:** Use `role="dialog"`, trap keyboard focus inside the modal while open, and restore focus to the trigger upon closing.
- **Live Updates & Toasts:** Use `aria-live="polite"` so screen readers announce incoming notifications without interrupting current speech.
3. Respecting prefers-reduced-motion
For users with vestibular disorders or motion sensitivities, rapid scaling, parallax scrolling, and bouncing springs can cause dizziness and nausea. Query the CSS media feature `@media (prefers-reduced-motion: reduce)` and replace physical translations with simple opacity fades.
4. Touch target sizes and spacing
WCAG 2.2 Success Criterion 2.5.8 requires target sizes of at least 24×24 CSS pixels, but mobile platform guidelines (Apple HIG and Android Material) recommend a minimum of 44×44 to 48×48 pixels to prevent accidental taps, especially for users with motor impairments.
In ExodeUI, which we make, interactive components compile to accessible vector representations and support reduced-motion overrides natively.