Tooltips and popovers do not preserve the trigger element's existing aria-describedby attribute value.
The aria-describedby attribute supports specifying multiple space separated element ID's.
When adding a tooltip or popover to an element that has an existing aria-describedby attribute, the attribute is removed. And when opened the attribute is set only to the auto generated tooltip/popover ID. When the tooltip (or popover) is closed, the original aria-describedby is not restored. (the attribute is completely removed)
The above codepen results in the following markup:
Noe that the original aria-describedby attribute is not present on the input element.
Expected behavior:
That the tooltip (or popover) ID is added to the existing aria-describedby attribute when opened, and when closed the tooltip/popover ID is removed from the aria-describedby attribute (leaving any original ids in the attribute). If there wasn't any aria-describedby attribute on the trigger element, then the attribute can be removed.
Tooltips and popovers do not preserve the trigger element's existing
aria-describedbyattribute value.The
aria-describedbyattribute supports specifying multiple space separated element ID's.When adding a tooltip or popover to an element that has an existing
aria-describedbyattribute, the attribute is removed. And when opened the attribute is set only to the auto generated tooltip/popover ID. When the tooltip (or popover) is closed, the originalaria-describedbyis not restored. (the attribute is completely removed)The above codepen results in the following markup:
Noe that the original
aria-describedbyattribute is not present on the input element.Expected behavior:
That the tooltip (or popover) ID is added to the existing
aria-describedbyattribute when opened, and when closed the tooltip/popover ID is removed from thearia-describedbyattribute (leaving any original ids in the attribute). If there wasn't anyaria-describedbyattribute on the trigger element, then the attribute can be removed.