live property
Indicates that an element will be updated, and describes the types of updates the user agents, assistive technologies, and user can expect from the live region.
The values of this attribute are expressed in degrees of importance. When regions are specified
as polite, assistive technologies will notify users of updates but generally do not interrupt
the current task, and updates take low priority. When regions are specified as assertive,
assistive technologies will immediately notify the user, and could potentially clear the speech
queue of previous updates. Please refer to Live Region Properties and How to Use Them (ARIA-PRACTICES,
Section 5.2.1).
Politeness levels are essentially an ordering mechanism for updates and serve as a strong suggestion to user agents or assistive technologies. The value may be overridden by user agents, assistive technologies, or the user. For example, if assistive technologies can determine that a change occurred in response to a key press or a mouse click, the assistive technologies may present that change immediately even if the value of the aria-live attribute states otherwise.
Since different users have different needs, it is up to the user to tweak his or her assistive technologies' response to a live region with a certain politeness level from the commonly defined baseline. Assistive technologies may choose to implement increasing and decreasing levels of granularity so that the user can exercise control over queues and interruptions.
When the property is not set on an object that needs to send updates, the politeness level is the value of the nearest ancestor that sets the aria-live attribute.
The aria-live attribute is the primary determination for the order of presentation of changes to live regions. Implementations will also consider the default level of politeness in a role when the aria-live attribute is not set in the ancestor chain (e.g., log changes are polite by default). Items which are assertive will be presented immediately, followed by polite items. User agents or assistive technologies MAY choose to clear queued changes when an assertive change occurs. (e.g., changes in an assertive region may remove all currently queued changes)
See: developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-live
Implementation
@override
@Accessor(key: 'aria-live')
dynamic get live => (props[_$key__live___$AriaPropsMixin] ?? null) as dynamic;Indicates that an element will be updated, and describes the types of updates the user agents, assistive technologies, and user can expect from the live region.
The values of this attribute are expressed in degrees of importance. When regions are specified
as polite, assistive technologies will notify users of updates but generally do not interrupt
the current task, and updates take low priority. When regions are specified as assertive,
assistive technologies will immediately notify the user, and could potentially clear the speech
queue of previous updates. Please refer to Live Region Properties and How to Use Them (ARIA-PRACTICES,
Section 5.2.1).
Politeness levels are essentially an ordering mechanism for updates and serve as a strong suggestion to user agents or assistive technologies. The value may be overridden by user agents, assistive technologies, or the user. For example, if assistive technologies can determine that a change occurred in response to a key press or a mouse click, the assistive technologies may present that change immediately even if the value of the aria-live attribute states otherwise.
Since different users have different needs, it is up to the user to tweak his or her assistive technologies' response to a live region with a certain politeness level from the commonly defined baseline. Assistive technologies may choose to implement increasing and decreasing levels of granularity so that the user can exercise control over queues and interruptions.
When the property is not set on an object that needs to send updates, the politeness level is the value of the nearest ancestor that sets the aria-live attribute.
The aria-live attribute is the primary determination for the order of presentation of changes to live regions. Implementations will also consider the default level of politeness in a role when the aria-live attribute is not set in the ancestor chain (e.g., log changes are polite by default). Items which are assertive will be presented immediately, followed by polite items. User agents or assistive technologies MAY choose to clear queued changes when an assertive change occurs. (e.g., changes in an assertive region may remove all currently queued changes)
See: developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-live
Implementation
@override
@Accessor(key: 'aria-live')
set live(dynamic value) => props[_$key__live___$AriaPropsMixin] = value;