• Media Type Web > ARIA and Dynamic Content > ARIA > Live Regions
  • State Active
  • Advisory No

To communicate the greatest amount of information about a user interface element and its relationship of live regions to users, assistive technologies need to understand the relationships that elements have to other elements on the page. Developers can indicate which controls are controlled by a live region by setting an attribute. When this attribute is not set, assistive technology will not be able to convey this relationship to the user.

Compliant Example

<input id="bc" type="button" aria-controls="lr"
value="Update"/>
...
<p id="lr" aria-live="polite">Initial Content</p>

Non-Compliant Example

<input id="bc" type="button" value="Update"/>
...
<p id="lr" aria-live="polite">Initial Content</p>

Specify which controls are controlled by the live region by using the "aria-controls" attribute. The "controls" attribute takes a list of IDREFS separated by spaces which reference elements that are controlled by the current element. If the target controls have their live attribute set to off, this could inform assistive technology to announce that a live region has been updated without announcing the actual update.

Note - When the WAI ARIA specification becomes an official recommendation of the W3C, ARIA related best practices such as this will become required under the relevant WCAG checkpoint (in this case 1.3.1).

Organization Standards

  • § 508-1194.22 Web Sites and Applications
    • (l) Ensure scripts are accessible
  • WCAG 2.0 Level A
    • 1.3.1 Information and relationships conveyed through presentation
  • WCAG 2.1 Level A
    • 1.3.1 Info and Relationships

Other Mapped Standards

  • § 508-1194.21 Software Applications and Operating Systems
    • (d) Information about a user interface element must be textually available
  • 47 CFR 14. Advanced Communication Services
    • 47 CFR 14.21 Performance Objectives
      • (b) Accessible
        • (b)(1) Input, control, and mechanical functions shall be locatable, identifiable, and operable
          • (b)(1)(i) Operable without vision
        • (b)(2) All information necessary to operate and use the product
          • (b)(2)(i) Availability of visual information
  • BITV 2.0 (Priority I)
    • 1.3.1 Informationen und Beziehungen
  • KWCAG
    • 4-1 - Ensure plug-ins are directly accessible
      • 4-1-1 - Ensure that the embedded content itself is accessible
  • NFB Certification
    • Client Side Content Changes
  • Telecommunications Act Accessibility Guidelines
    • 1193.41 Input, control, and mechanical functions.
      • (a) Operable without vision. Provide at least one mode that does not require user vision.
    • 1193.43 Output, display, and control functions.
      • (a) Availability of visual information. Provide visual information through at least one mode in auditory form.
  • WCAG 1.0 Priority 1
    • 08.1 Ensure programmatic elements such as scripts and applets are accessible
  • WCAG 1.0 Priority 2
    • 06.5 Ensure dynamic content is accessible.
    • 11.1 Use the latest W3C technologies.
  • WCAG 2.2 Level A (Draft August 11, 2020)
    • 1.3.1 Info and Relationships
  • Severity

    4 (yellow)
    in range of 1 to 10
  • Noticeability

    3 ()
    in range of 1 to 10
  • Tractability

    3 ()
    in range of 1 to 10