Dynamic Content – Accessibility Guidelines

Name, Role, Value #

For all user interface components (including, but not limited to, form elements, links, and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies (Level A).

Development Considerations

• Provide the name, role, state, value of all components.
• For each element a user encounters, they need to know:
  • Name (e.g., the label)
  • State (e.g., checked/unchecked, expanded/collapsed, selected/unselected)
  • Role (e.g., input type)
  • Value

Pause, Stop, Hide #

For moving, blinking, scrolling, or auto-updating information, ALL of the following are true:

• Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it, unless the movement, blinking, or scrolling is part of an activity where it is essential; and
• Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it, or to control the frequency of the update, unless the auto-updating is part of an activity where it is essential.

Failure to meet this requirement could interfere with any use of the page. Refer to Requirement 5 – Non-Interference to learn more.

Content/Design Considerations

• Best Practice: Do not use content that automatically moves, blinks, or scrolls.
• User must be able to configure auto-updates to content.