---
name: accessibility
description: Build and review inclusive product experiences. Use when creating or changing user interfaces, interaction flows, forms, media, documents, validation, navigation, or any user-visible feature that needs keyboard, assistive-technology, visual, motor, cognitive, or motion consideration.
---

# Accessibility

## Make inclusion a build constraint

Treat accessibility as part of the feature, not final polish. Use the most semantic, platform-native structure available and provide clear names, instructions, relationships, and status feedback.

Ensure every essential action and flow works without a pointer and with assistive technology. Keep focus visible, ordered, and intentionally moved after navigation or dynamic updates. Make errors understandable, connected to their cause, and recoverable.

## Avoid single-channel communication

Provide sufficient contrast and readable type. Do not use colour, sound, animation, position, or a gesture as the only way to understand or complete a task. Respect text scaling, zoom, reduced-motion preferences, and alternative input methods.

## Verify the interaction

Test the changed flow using keyboard-only interaction and the applicable platform accessibility tools. Check labels, focus, announcements, state changes, validation, and custom controls. Report the checks actually performed and any remaining limitations.