Product
axe-core
Product Version
4.10.2
Latest Version
Issue Description
Expectation
I expect landmark roles to be identified correctly.
I expect values for aria-labelledby to be correctly differentiated.
Actual
Screenshot:

I have a section element with the role of tabpanel. There are several tabpanels, and they are all given a unique accessible name through the aria-labelledby attribute. Visible in the screenshot are those values.
- My first issue is that an element with the role of
tabpanel is not a landmark element.
- My second issue is that I did not expect to receive an error about unique AccNames, when the values for each
aria-labelledby attribute are unique ID values. However, if the tool is actually replacing the ID with the text value for that ID, then this would not be a false positive (since this is on a page with several demo versions of a component).
How to Reproduce
Hopefully the attached screenshot is enough information to reproduce the issue. If not, please let me know.
Product
axe-core
Product Version
4.10.2
Latest Version
Issue Description
Expectation
I expect landmark roles to be identified correctly.
I expect values for aria-labelledby to be correctly differentiated.
Actual
Screenshot:

I have a
sectionelement with the role oftabpanel. There are several tabpanels, and they are all given a unique accessible name through thearia-labelledbyattribute. Visible in the screenshot are those values.tabpanelis not a landmark element.aria-labelledbyattribute are unique ID values. However, if the tool is actually replacing the ID with the text value for that ID, then this would not be a false positive (since this is on a page with several demo versions of a component).How to Reproduce
Hopefully the attached screenshot is enough information to reproduce the issue. If not, please let me know.