For systems that include static and interactive components, people may need interactive components to be clearly distinguishable visually and programmatically from static content.
Notes
Partial 4.2.5 Making Content Usable
Examples:
- Disabled buttons gray out with a contrast that sufficiently different compared to the enabled state.
- A screen reader announces actionable elements, such as buttons and links (including if they are in a disabled state) because of good markup.
- Actionable buttons are backlit with an LED.
- An error tone is given immediately when a person try to type text in a field that does not currently accept text input.
- Fields that are not available in the current context are hidden, so there is no need to distinguish between actionable and non-actionable components.
Mappings
References
Tags
Imported from https://github.com/accessiblecommunity/Digital-Accessibility-Framework/distinguish-if-actionable.md