Accessibility Required Modifier

Activation

Activate when a user interface must be usable by people with diverse visual, auditory, motor, or cognitive access needs.

Required effects

Select testing-strategy: integration-balanced. Define semantic structure, accessible names, keyboard behavior, focus order and restoration, announcements, contrast, motion, scaling, errors, and time constraints as product behavior. Prefer native semantics and verify representative assistive-technology and keyboard paths alongside automated checks.

Prohibitions and review

Do not replace native semantics with visual imitation, remove focus indicators, encode meaning by color alone, or treat an automated score as complete evidence. Accessibility exceptions require a documented constraint, safe alternative, and follow-up condition.