Regarding the current level of support with the tested screen readers, this situation did not arise. Defines a string value that labels the current element. The average includes all versions, but some browser/AT combinations have tests for multiple versions (NVDA / JAWS / VoiceOver), Ist das aria-current-Attribut gesetzt, so sollen Screenreader und andere Hilfsmittel das Element semantisch identifizieren (z.B. The heading role and aria-level attribute should only be used to retrofit accessibility on legacy code that you cannot make major changes to. aria-current="location" Whenever a website hierarchy is deeply nested, it's often a good practice to display the hierarchy of a given page using the Breadcrumbs Pattern. A few hours ago I read about the aria-label attribute, which:. ARIA role and attribute support in different screen reader / browser combinations. This is why I included it in the aria-label . „page“ repräsentiert die aktuelle Seite innerhalb eines Satzes von Webseiten (z.B. Tel: +49(231) 58054815 I looked further in the Mozilla Developer Network to get some examples and explanations, but the only thing I found was X Tests expected to fail (due to authoring errors) are marked with . aria-label is a description that is never displayed on screen but is relayed to the screen reader user. Screen readers allow users to interact in different modes, and can produce very different results in each mode. Although theoretically you can go higher, and some screen readers may support it, the results can be unpredictable with other browser/screen reader combinations. aria-details does not contribute to the computation of an element’s accessible name or description. 44139 Dortmund Code used for this test: oder