- Page URL
- https://www.telekom.de/unterwegs/hersteller/apple/apple-watch-familienkonfiguration
Issues List
Non-text Content
1.1.1 (A)
Image text alternative does not serve equivalent purpose
+
Non-text Content
1.1.1 (A)
Image is decorative but has text alternative
+
Info and Relationships
1.3.1 (A)
Visual presentation of heading structure does not match code markup
+
Info and Relationships
1.3.1 (A)
Visual presentation of elements does not match code markup
+
Info and Relationships
1.3.1 (A)
Semantic HTML elements are used for styling or layout purposes
+
Use of Color
1.4.1 (A)
Links are indicated by color only
+
Use of Color
1.4.1 (A)
Interactive element's hover state indicated by color only
+
Contrast (Minimum)
1.4.3 (AA)
Text content does not have enough color contrast
+
Reflow
1.4.10 (AA)
Horizontal scrolling available on smaller viewports
+
Text Spacing
1.4.12 (AA)
Text content overflows containers with user changed text spacing
+
Keyboard
2.1.1 (A)
Interactive element, operable by mouse, not accessible by keyboard
+
Keyboard
2.1.1 (A)
Dialog window does not receive keyboard focus
+
Page Titled
2.4.2 (A)
Page title missing space
+
Focus Order
2.4.3 (A)
User-activated dynamic content not in correct focus order
+
Link Purpose (In Context)
2.4.4 (A)
Purpose of link cannot be programmatically determined
+
Link Purpose (In Context)
2.4.4 (A)
Link to PDF document does not indicate so
+
Headings and Labels
2.4.6 (AA)
Headings do not accurately describe purpose / content
+
Focus Not Obscured (Minimum)
2.4.11 (AA)
Dialog windows obscure focus of underlying elements
+
Name, Role, Value
4.1.2 (A)
Interactive element uses non-semantic HTML
+
Name, Role, Value
4.1.2 (A)
Interactive element uses non-semantic HTML
+
Accompanying Files
Observation Details
Purely decorative images must not have an accessible text alternative present. They must be excluded from the accessibility tree.
See used icons in screenshots.
Remediation Notes
Ensure, all purely decorative images are not accessible by assistive technology. Depending on the way, in image is embedded, the following methods can be used to remove it from the accessibility tree:
HTML image element: Set a null alt attribute as follows:
<img alt="" />; do not use ARIA to hide the HTML image elementHTML SVG element: Remove the SVGs
<title>element or keep it empty and use ARIA to explicitly hide the element to ensure highest compatibility across browsers and assistive technology:<svg aria-hidden="true">
Accompanying Files
Observation Details
Images that are not purely decorative, must have a purpose equivalent text alternative set, to be accessible if the image cannot be visually perceived. A prime example is a blind screen reader user. But also if an image cannot be loaded due to network issues, the text alternative ensures perception of the conveyed information.
All images have non-equivalent text alternative:
Apple Watch Familienkonfiguration
Immer in Verbindung mit der Apple Watch für Kinder und Smart Connect M
Sorgenfreier dank der Apple Watch für Kinder
Jetzt Apple Watch SE mit Smart Connect M bestellen
Remediation Notes
Ensure purpose equivalent text alternatives are present for every non-decorative image. Depending on the purpose, the text alternative may be describing the contents of an image or the functionality it serves (e.g. as a link to a specific page).
Apple Watch Familienkonfiguration
"iPhone mit Einrichtungsbildschirm der Familienkonfiguration. Drei Apple Watches zeigen verschiedene Funktionen. Eine Watch eingerichtet für Opa, zeigt iMessage Konversation. Eine Watch eingerichtet für Mama zeigt Standort von Kind Luis. Eine Watch eingerichtet für Kind Luis zeigt eingehenden Anruf von Papa."
Immer in Verbindung mit der Apple Watch für Kinder und Smart Connect M
arguably, this image is decorative; if not:
"Mama und Tochter formen mit ihren Händen gemeinsam ein Herz in der Luft"
Sorgenfreier dank der Apple Watch für Kinder
arguably, this image is decorative; if not:
"Papa umarmt Sohn von hinten. Beide lächeln in die Kamera"
Jetzt Apple Watch SE mit Smart Connect M bestellen
"Apple Watch SE in Farbe Polarstern"
Observation Details
Links solely rely on color to be differentiated from other, surrounding text content and color contrast ratio of link text color to surrounding text color does not meet minimum required 3:1 color contrast ratio. Links, relying on color only and with insufficient color contrast ratio to surrounding text content include:
"MagentaEins" in "Unser Tipp für Mobilfunkkunden"
"Zusatzkarte" in
"Weitere Angebote für Ihre Apple Watch"
FAQ item "Was sind die Vorteile der Apple Watch für Kinder?"
"Smart Connect" in FAQ item "Welcher Telekom Tarif eignet sich für die Apple Watch für Kinder?"
Remediation Notes
Ensure, links can be differentiated from surrounding text content by at least one other visually perceivable factor. Preferably use underline to indicate link text as it is browser default and known pattern to users.
Accompanying Files
Observation Details
Hovering interactive element adds visual indicator that does solely rely on color to be differentiated from default state and color contrast ratio of default and hover states does not meet minimum required 3:1 color contrast ratio.
"Zum Angebot" link in "Die Apple Watch ist für alle da. Auch wenn Sie noch kein iPhone haben."
Remediation Notes
Side note: the "link" has no href attribute, removing any functionality from the wanted link. This also is a failure of 4.1.2 Name, Role, Value. Ensure, all HTML <a> elements have a non-null href attribute set.
Accompanying Files
Observation Details
Text content must meet minimum color contrast ratio of 4.5:1 to its background. Large text (>24px) content must meet minimum color contrast ratio of 3:1 to its background. The following text content does not meet the required minimum contrast ratios:
Link "Zusatzkarte" in FAQ item "Was sind die Vorteile der Apple Watch für Kinder?"
Link "Smart Connect" in FAQ item "Welcher Telekom Tarif eignet sich für die Apple Watch für Kinder?"
Remediation Notes
Ensure, all text content is clearly visible, using color contrast ratios of 4.5:1 and higher. For large text content a reduced contrast ratio of 3:1 is acceptable, but not recommended.
Especially color variants that barely meet color contrast ratio requirements for default background colors are subsceptible to fail minimum color contrast ratio, when used on non-default background colors. When a certain color barely meets color contrast ratio on default white background, ensure, this color variant is only used on said background color and provide a different foreground color variant for darker background colors.
Ideally, aim for enhanced contrast ratio 7:1 (see 1.4.6 Contrast (Enhanced) (Level AAA)), to often ensure passing minimum contrast ratio, even on non-default background colors.
Side Note: this success criterion is not specifically about identification of links. When a link would have no underline and its color is the only way to differentiate from surrounding text, it is considered a failure under 1.4.1 Use of Color. This criterion is for all text content.
Accompanying Files
Observation Details
Setting the viewport width to 320px allows for horizontal scrolling. As no actual content is overflowing the viewport, this is not considered a failure of 1.4.10 Reflow. It should however still be investigated and fixed.
Remediation Notes
No remediation notes given, as the observation is not considered a failure.
Accompanying Files
Observation Details
Text content and images in certain containers may overflow the container's boundaries, when text spacings are changed, making some text harder, other text impossible to perceive. This often includes:
Stage areas
Badges
Buttons
Manually outlined elements like buttons (e.g. footnote icon buttons)
Teasers
Card components
Remediation Notes
Container elements must not use fixed dimensions, if they contain text content, to allow proper reflow without obscuring / overlapping content. Changing text spacings to values
Line height (line spacing) to at least 1.5 times the font size;
Spacing following paragraphs to at least 2 times the font size;
Letter spacing (tracking) to at least 0.12 times the font size;
Word spacing to at least 0.16 times the font size.
must be possible and must not lead to any loss of content or functionality.
Observation Details
This is not considered a failure, just a side note:
Page title "Apple Watch für Kinder| Telekom" is missing a space before pipe character. Ideally, to be consistent, the second part of the page title is automatically generated, reducing proneness to errors.
Observation Details
When dynamically added content can be activated by the user, correct focus order must be ensured. This includes:
Opening a dialog window
Expanding an accordion item
Dynamically loading more content (e.g. more products in a product list) via "Load more" button
Adding and removing dynamic content must not remove focus from the triggering element. E.g. a footnote or info icon opening (adding) a dialog window. When the dialog window is closed (removed) again, focus must be on the triggering element.
Remediation Notes
Ensure, for all dynamically added content that can be activated by user,
focus cannot be set to focusable elements inside content, before content is being visually added (e.g. collapsed accordion items, or not yet opened dialog windows)
dynamic content should be placed directly below the triggering element in the DOM order
Opening e.g. a dialog window, will set the focus on the first focusable element inside the dialog window
Activating a "Load more" button must ensure, focus, after content is loaded, either
is set to the first focusable element of newly loaded content or
is set to the first preceding focusable element of newly loaded content.
Ensure, for all dynamically added and then removed content that can be activated by user,
keyboard focus
remains (e.g. collapsing/expanding accordion items) on the triggering element or
is set to (e.g. opening and closing a dialog window) the triggering element again.
Accompanying Files
Observation Details
Context of "Jetzt als Zweitkarte buchen"
preceding heading, level 2: "Unser Tipp für Mobilfunkkunden"
preceding heading, level 1: "Apple Watch für Kinder"
Context implies "Jetzt Apple Watch für Kinder als Zweitkarte buchen"
The purpose of a link must not solely rely on visually perceived aspects like layout, proximity, placement. The purpose of a link should be understandable from the link text itself or its programmatic context, ensuring it's accessible to assistive technologies and a wider range of users.
Relying solely on visual cues to convey a link's purpose makes it inaccessible to:
Users of assistive technology like screen readers.
Users with cognitive disabilities who might not interpret visual layouts correctly.
Users with customized displays (e.g. unexpected viewport sizes, or turned off styles).
Remediation Notes
As interactive elements, links must have accessible names. Ensure, HTML link elements are not "empty", i.e. without link text content.
Ensure, link purpose can be determined from link text content or its programmatic context. Ideally, the link text itself will convey the link purpose. If it is not possible to use link text content, proper programmatic context may be:
the link's surrounding paragraph, if the paragraph itself has the purpose to introduce the link and is not too long, as e.g. a user of assistive technology would have to perceive the paragraph in full to understand the link purpose.
the link's directly preceding heading (e.g. the heading of a product card may be used to determine the purpose of this card's CTA link)
This issue can be fixed, ensuring accurate heading structure. See 1.3.1 Info and Relationships and 2.4.6 Headings and Labels for more information.
Observation Details
Open dialog windows can obscure focus of underlying interactive elements. Obscuring can be partial or complete. This will impact users of keyboard navigation as focus cannot be tracked while a dialog window is open. Dialog windows may be triggered by:
Footnotes
Info Icons
Buttons
Remediation Notes
When opened,
dialog windows must receive keyboard focus and
keyboard focus must be trapped inside the dialog window.
Ensuring placed and trapped keyboard focus to the opened dialog window will remediate this issue, as no interactive element outside of the opened dialog window should be focusable, thus cannot be focus obscured.
For more information about technical requirements of modal dialogs, refer to BFIT-Bund Handreichung "Accessible design of user interface elements – Modal Dialog". Also, consider/evaluate use of HTML dialog element <dialgo>. See HTML specifications – The dialog element and Can I Use – Dialog for browser support information.
Observation Details
When opening a dialog window (e.g. via footnote or info icon), said dialog window does not receive keyboard focus. This leads to multiple issues:
The contents of the dialog window are not accessible via keyboard.
The dialog window can not be closed by keyboard (easily or at all).
While the dialog window is open, keyboard navigation of the underlying page is still possible; the dialog window however blocks the view. (see also 2.4.11 Focus Not Obscured (Minimum))
Since keyboard navigation stays possible, opening multiple dialog windows above each other also is possible.
Remediation Notes
Opening a dialog window by keyboard navigation must set the focus to the dialog window's content. Opening a dialog window must trap keyboard focus inside the dialog window, so underlying content cannot be accessed while dialog window is opened. Closing the dialog window, focus must be set to the triggering element again.
Ideally, the first focusable element in a dialog window can be used to close the dialog window, so opening and closing of a dialog window can be done without the need of navigating through other focusable elements. Although simple dialog windows, e.g. asking for confirmation, and providing "Accept" and "Cancel" buttons, might not have an explicit "Close" button and may set focus to the dialog window's "main purpose action" instead.
Accompanying Files
Observation Details
Interactive element can be operated by mouse but not by keyboard. The issue may occur when:
Non-semantic HTML elements (e.g.
<div>,<span>) are used for interactive purposes (e.g. links, buttons, inputs), instead of semantic HTML elements (e.g.<a href="">,<button>). This often also leads to other issues, concerning 4.1.2 Name, Role, Value.Semantic elements are used but required attributes are missing (e.g.
<a>, missinghrefattribute)Semantic HTML elements are mis-used (e.g.
<a>used as a button, or<button>used as a link)
Remediation Notes
Ensure, using native, semantic HTML elements for interactive elements and not re-building existing functionality with generic elements like <div> and <span>.
Ensure, choosing the proper elements, depending on purpose (e.g. links, using <a href=""> to link to resources, and <button> to perform actions).
This way, the need for added JavaScript (e.g. on click events / event handlers) and ARIA methodologies is reduced to a minimum, which will ensure clean and simple code and backwards compatibility, will future-proof functionality, and will avoid issues with keyboard navigation or other assistive technology (see also 4.1.2 Name, Role, Value).
Observation Details
The visually presented heading structure of the page does not match the use of semantic HTML heading elements. The visually presented structure is as follows:
h1 Die Apple Watch ist für alle da. Auch wenn Sie noch kein iPhone haben.
h2 Vorteile für Ihre Kids
h2 Vorteile für die Erwachsenen
h2 Ihre Vorteile mit Smart Connect M
h2 Jetzt Apple Watch SE mit Smart Connect M bestellen
h2 Unser Tipp für Mobilfunkkunden
h2 Weitere Angebote für Ihre Apple Watch
h2 Häufig gestellte Fragen zur Apple Watch für Kinder
h3 Was sind die Vorteile der Apple Watch für Kinder?
h3 Gibt es einen Unterschied zwischen ...
h3 Welcher Telekom Tarif eignet sich für die Apple Watch für Kinder?The programmatically determinable heading structure, using HTML heading elements is as follows:
h1 Apple Watch für Kinder
h2 Immer in Verbindung mit der Apple Watch und Smart Connect M
h3 Vorteile für Ihre Kids
h2 Sorgenfreier dank der Apple Watch für Kinder
h3 Vorteile für die Erwachsenen
h2 Passend für Apple Watch Nutzer
h3 Ihre Vorteile mit Smart Connect M
h2 Jetzt Apple Watch SE mit Smart Connect M bestellen
h2 Unser Tipp für Mobilfunkkunden
h2 Die Apple Watch für Kinder – auch für alle
h3 Weitere Angebote für Ihre Apple Watch
h2 Häufig gestellte Fragen zur Apple Watch für KinderObservations for heading structure:
Visual main heading not
<h1>; not even any heading at allHeading eyebrows use separate heading elements
FAQ items do not use headings
Remediation Notes
Ensure, visually presented heading structure matches programmatically determinable heading structure by only using HTML heading elements for heading content and using HTML heading elements for all heading content.
Side note: This criterion does not specifically look at proper heading content (i.e. wordings, usefulness of headings). See 2.4.6 Headings and Labels for this.
Accompanying Files
Observation Details
Semantic HTML elements must not be used for styling and layout purposes. Semantic elements carry a certain role that is communicated to assistive technology. Using semantic elements with a certain role for styling or layout purposes while the content does not match the communicated role, it will confuse users of assistive technology. Certain elements will be announced in certain ways, so that e.g. line break elements <br> or empty paragraph elements <p></p> are announced as "empty group".
Remediation Notes
Ensure proper use of semantic HTML.
Semantic elements must not solely be used for styling or layout purposes
All styling and layout changes must use CSS
Limit use of line breaks to intended purposes, e.g. in poetry or code snippets
Accompanying Files
Observation Details
<dl> element used for non-list content in FAQ accordion.
These mis-matches happen with improper use of semantic HTML or lack thereof. Content, visually presented in a certain way, communicating certain purpose or functionality, uses mis-matched HTML elements.
This occurs in two "directions". Visually presented as X, using element Y, and using element X, while content is non-X content. The former includes:
Links, using HTML elements other than
<a href="">Buttons, using HTML elements other than
<button>Input elements, not using appropriate semantic HTML elements for e.g. selects or text inputs with
typeattributesHeadings, using HTML elements other than
<h1>-<h6>Lists, not using
<ul>,<ol>,<dl>...
The latter includes, using semantic HTML elements for content that does not fit the semantically conveyed role of that element, includes:
Lists for non-list content
Headings for non-heading content
...
Improper use of semantic HTML leads to numerous issues for many users, also affecting other success criteria at the same time, including those, ensuring keyboard navigation and accessible use of assistive technology.
Remediation Notes
Ensure proper use of semantic HTML.
Elements with needed or wanted functionality use the native HTML element, fitting said functionality
Links use
<a href="">Buttons use
<button>Lists use
<ul>,<ol>,<dl>; this includes all list content (e.g. navigations and lists of articles / cards)Headings use
<h1>,<h2>,<h3>,<h4>Emphasis of text content uses
<strong>and<em>instead of<b>and<i>...
Only content with that functionality uses said HTML elements.
No grouping for layout or styling is done, using semantic HTML elements; use
<div>and<span>onlyNo styling is done, using semantic HTML elements; this includes creating paragraphs with line break elements or spacings with empty paragraphs
Observation Details
The heading structure should work as an outline of the complete page content, with the main heading describing the page as a whole, and subsequent headings describe the content until another heading of same heading level is reached. This means, a heading level 2 must describe purpose of all content, including sub-heading levels and their content, until the next heading level 2 is reached.
The programmatically determinable heading structure, using HTML heading elements is as follows:
h1 Apple Watch für Kinder
h2 Immer in Verbindung mit der Apple Watch und Smart Connect M
h3 Vorteile für Ihre Kids
h2 Sorgenfreier dank der Apple Watch für Kinder
h3 Vorteile für die Erwachsenen
h2 Passend für Apple Watch Nutzer
h3 Ihre Vorteile mit Smart Connect M
h2 Jetzt Apple Watch SE mit Smart Connect M bestellen
h2 Unser Tipp für Mobilfunkkunden
h2 Die Apple Watch für Kinder – auch für alle
h3 Weitere Angebote für Ihre Apple Watch
h2 Häufig gestellte Fragen zur Apple Watch für KinderTo determine the accuracy of a heading's wording, a heading can be looked at in hierarchy up to the main heading. E.g. the first heading level 3, put in hierarchy context, is as follows:
h1Apple Watch für Kinder
h2Immer in Verbindung mit der Apple Watch und Smart Connect M
h3Vorteile für Ihre Kids
pEine neue Apple Watch oder ggf. auch das Vorgängermodell von Mama oder Papa kann jetzt ganz einfach und unkompliziert von Kindern genutzt werden. Die Eltern nach der Schule anrufen, die Großeltern über die gute Note per Nachricht informieren oder endlich ein eigenes Memoji an Freunde versenden – das alles und noch vieles mehr – ist mit der Apple Watch für Kinder jetzt möglich. Außerdem kann man mit den überarbeiteten Aktivitätsringen mit der Watch Bewegungsminuten spielend tracken, damit Bewegung noch mehr Spaß macht.
Observations, shown at the example heading above:
Heading hierarchy implies purpose "Vorteile für Kids, die mit der Apple Watch und Smart Connect M immer in Verbindung sind"
While not specifically for children, the content shows "Vorteile", so the
<h3>is more or less accurately describing content purposeThe
<h2>however does not add to this purpose at allAlso, usually, a heading element, followed by another heading element directly, without any content between, is a good indication of unnecessary heading hierarchy
To demonstrate this, it often is useful to look at the page outline one hierarchy level at a time, evaluating if headings level 2 accurately split the page into useful sections.
h1 Apple Watch für Kinder
h2 Immer in Verbindung mit der Apple Watch und Smart Connect M
h2 Sorgenfreier dank der Apple Watch für Kinder
h2 Passend für Apple Watch Nutzer
h2 Jetzt Apple Watch SE mit Smart Connect M bestellen
h2 Unser Tipp für Mobilfunkkunden
h2 Die Apple Watch für Kinder – auch für alle
h2 Häufig gestellte Fragen zur Apple Watch für KinderObservations for heading structure in general:
"Immer in Verbindung mit der Apple Watch und Smart Connect M"
Expected content: Apple Watch tariff Smart Connect M
Actual content: Generic text content about Apple Watch "Vorteile"
→ not accurate
"Sorgenfreier dank der Apple Watch für Kinder"
Expected content: Security features, privacy features, parenting features, ...
Actual content: "in Verbindung bleiben", app and contact management as administrator, location access
→ accurate
"Passend für Apple Watch Nutzer"
Expected content: ?
Actual content: "Vorteile" of Smart Connect M tariff
→ factually accurate, but wording does not hint on any specific content at all
"Jetzt Apple Watch SE mit Smart Connect M bestellen"
Expected content: Watch + tariff offer details and possibility to buy
→ accurate
"Unser Tipp für Mobilfunkkunden"
Expected content: Current customer offer for Apple Watch
Actual content: Offer for tariff as "Zweitkarte"
→ arguably not accurate
"Die Apple Watch für Kinder – auch für alle"
Expected content: ?
Actual content: Apple Watch features also useful for the elderly; MultiSIM offer
→ not accurate; wording does not hint on actual content
"Häufig gestellte Fragen zur Apple Watch für Kinder"
Expected content: FAQ about Apple Watch für Kinder
Actual content: "Vorteile der Apple Watch für Kinder", Difference between "Apple Watch Familienkonfiguration" and "Apple Watch für Kinder", Tariff for Apple Watch für Kinder
Observations:
"Vorteile" duplicates page content
"Unterschied Familienkonfiguration": Wording "Familienkonfiguration" was not used before (except in URL path); If "Familienkonfiguration" and "Apple Watch für Kinder" is not the same, the URL path, the page title, and the page's main heading do not match
"Tarif" duplicates page content
→ factually accurate, but not adding any information that is not already present on page
These observations can be done for each subsequent heading level as well.
Remediation Notes
HTML heading elements are the main way to navigate a page's structure. While sighted users also always benefit from accurate headings and heading structure, users of assistive technology often completely rely on them. Thus, headings must accurately describe their following content(s' purpose). A user of assistive technology may navigate a page by receiving a list of headings, starting with one hierarchy level at a time, as demonstrated in the observation details.
Headings that lead the users to have no expectations might result in the user not consuming the section's content at all. Headings that lead users to have specific expectations not being met by actual content might result in the user not consuming the section's content at all, expecting the content is not useful for them, or in the user consuming the section's content, expecting specific information, but not finding it.
To ensure accurate heading structure, it is important to look at the page outline one hierarchy level at a time, thinking about it like a magazine or newspaper. When the sports section (heading level 2) is of no interest to the user, but the local news section (heading level 2) is, the user might not even look at the sports section. If the sports section now holds local, sports-related news, the user might've wanted to consume, but didn't.
Splitting a given page into accurate, useful sections (heading level 2) first will ensure proper grouping of content. Example:
h1 Apple Watch für Kinder
h2 Vorteile
h2 Angebote
h2 Häufig gestellte FragenExpanding on that, adding a third hierarchy level:
h1 Apple Watch für die ganze Familie
h2 Vorteile
h3 Für Kids
h3 Für Eltern
h3 Für ältere Familienmitglieder
h2 Angebote
h3 Der passende Tarif – Smart Connect M
h3 Apple Watch SE mit Tarif im Bundle
h3 Tipp für bestehende Mobilfunkkunden
h3 Apple Watch mit bestehendem Tarif nutzen
h2 Häufig gestellte Fragen
h3 ...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".
Observation Details
Footnote button in section "Jetzt Apple Watch SE mit Smart Connect M bestellen" is marked up as follows:
<span
data-url="/unterwegs/ajax?ssb_block=dynamic-mapping&toGet=footnotes-popup&productId=tariff:16309"
class="..."
data-tealium-rel="content"
id="legal-notes-18794751934">
::before
</span>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
Use semantic HTML button element <button> instead.
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 – Button" for technical requirements for building interactive user interface components (buttons).
Observation Details
Link "Apple Watch mit MultiSIM" links to PDF document FLY_01_O23091_WBM_Apple_Liporello_RZ.indd. This is not indicated at the link or in the link's context (surrounding content).
While not a strict failure of success criterion 2.4.4 Link Purpose, it is considered best practice to indicate such unexpected behavior. Using visual and text content in expected ways, ensures good user experiences, not only for users of assistive technology but for all users. In this realm, the differences of links <a href="..."> and buttons <button> usually are indicated visually. Clicking a link, a user expects moving to a new resource. Clicking a button, a user expects to (usually) stay on the resource and performing an action, like opening a dialog window, adding a product to a cart, expanding/collapsing accordion items, etc.
Clicking a visual button "Apple Watch mit MultiSIM" that is used as a link already is unexpected behavior given "button vs. link". Linking to a PDF document then is further unexpected behavior that ideally should be indicated prior to the user's action.