label property
Defines a string value that labels the current element. See related aria-labelledby.
The purpose of aria-label is the same as that of aria-labelledby. It provides the user with a recognizable name of the object. The most common accessibility API mapping for a label is the accessible name property.
If the label text is visible on screen, authors SHOULD use aria-labelledby and SHOULD NOT
use aria-label. There may be instances where the name of an element cannot be determined programmatically
from the content of the element, and there are cases where providing a visible label is not
the desired user experience. Most host languages provide an attribute that could be used to
name the element (e.g., the title attribute in HTML HTML
), yet this could present a browser
tooltip. In the cases where a visible label or visible tooltip is undesirable, authors MAY
set the accessible name of the element using aria-label. As required by the text alternative
computation, user agents give precedence to aria-labelledby over aria-label when computing
the accessible name property.
See: developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-label
Implementation
@override
@Accessor(key: 'aria-label')
String? get label =>
(props[_$key__label___$AriaPropsMixin] ?? null) as String?;
Defines a string value that labels the current element. See related aria-labelledby.
The purpose of aria-label is the same as that of aria-labelledby. It provides the user with a recognizable name of the object. The most common accessibility API mapping for a label is the accessible name property.
If the label text is visible on screen, authors SHOULD use aria-labelledby and SHOULD NOT
use aria-label. There may be instances where the name of an element cannot be determined programmatically
from the content of the element, and there are cases where providing a visible label is not
the desired user experience. Most host languages provide an attribute that could be used to
name the element (e.g., the title attribute in HTML HTML
), yet this could present a browser
tooltip. In the cases where a visible label or visible tooltip is undesirable, authors MAY
set the accessible name of the element using aria-label. As required by the text alternative
computation, user agents give precedence to aria-labelledby over aria-label when computing
the accessible name property.
See: developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-label
Implementation
@override
@Accessor(key: 'aria-label')
set label(String? value) => props[_$key__label___$AriaPropsMixin] = value;