Observation Details
"Zum Angebot" link does not use <a href=""> but omits href attribute. Clicking the link scrolls the page to the desired location but does not set focus correctly. Using assistive technology, clicking the link will keep the focus on the triggering element.
All interactive elements that do not use native, interactive HTML elements must be built in a way, that semantic information is provided and updates to semantic information are accessible via assistive technology. Building interactive components with non-semantic HTML elements results in inaccessible content. These accessibility issues might occur:
Interactivity of element is not announced → user will not know, that element is interactive
Changes to states (e.g. collapsed/expanded) is not announced → user will not know of the change
Target resource is not announced → e.g. user will not know, where a link leads to
Interactive action is not announced → e.g. user will not know, that a dialog window will be opened
Issues in 4.1.2 Name, Role, Value often occur together with other issues e.g. in 2.1.1 Keyboard and 2.4.7 Focus Visible.
Remediation Notes
Ensure, all HTML link elements use the mandatory href attribute correctly. Linking to an existing id="anchor-id", the appropriate <a href="#anchor-id"> syntax must be used.
Using non-native, non-semantic HTML elements to build functionality, native, semantic HTML elements already provide should be a rare occasion. As the first rule of ARIA use describes, if there is a semantic HTML with needed or wanted functionality this should always be used instead of ARIA.
Ensure, semantic HTML elements are used for all interactive elements and components. Refer to BFIT-Bund Handreichung "Accessible design of user interface elements" for technical requirements for building interactive user interface components. Building a link, not using existing, semantic <a href="..."> syntax, requires dramatically more maintenance, as shown on BFIT-Bund Handreichung "Accessible design of user interface elements – Link".