Page URL
https://www.telekom.de/shop/iot/kinderuhr-mit-gps

Issues List

Non-text Content 1.1.1 (A)
Image "Was ist das Besondere an der Anio Kinderuhr mit GPS?" does not have purpose equivalent text alternative
Non-text Content 1.1.1 (A)
Image(s) "Die GPS-Kinderuhr – so individuell wie Ihr Kind" do not have purpose equivalent text alternatives
Non-text Content 1.1.1 (A)
Video still images for video player dialog windows do not have purpose equivalent text alternatives
Non-text Content 1.1.1 (A)
Image "Schulmodus" does not have purpose equivalent text alternative
Non-text Content 1.1.1 (A)
Informative images (checkmark / cross) in table do not have purpose equivalent text alternative
Non-text Content 1.1.1 (A)
Decorative icons have non-null alt attribute set
Non-text Content 1.1.1 (A)
App store / Play store icons used as functional images do not have purpose equivalent text alternative
Audio-only and Video-only (Prerecorded) 1.2.1 (A)
Video "SOS-Knopf in Aktion" has no media alternative
Captions (Prerecorded) 1.2.2 (A)
Video "Was Eltern über die GPS-Kinderuhr Anio 6 sagen:" does not provide captions
Captions (Prerecorded) 1.2.2 (A)
Video "So verbinden Sie die GPS-Kinderuhr mit Ihrem Smartphone" does not provide captions
Audio Description or Media Alternative (Prerecorded) 1.2.3 (A)
Video "Was Eltern über die GPS-Kinderuhr Anio 6 sagen" has no audio description
Info and Relationships 1.3.1 (A)
Visual presentation of elements does not match code markup
Info and Relationships 1.3.1 (A)
Visually presented heading structure does not match code markup
Info and Relationships 1.3.1 (A)
Semantic HTML elements are used for styling or layout purposes
Info and Relationships 1.3.1 (A)
Improper use of semantic HTML list elements
Info and Relationships 1.3.1 (A)
Text content not always accessible to assistive technology
Meaningful Sequence 1.3.2 (A)
Sequence main heading → badge
Contrast (Minimum) 1.4.3 (AA)
Text of visited link in Direkteinstiege barely visible
Resize text 1.4.4 (AA)
Content overflows when text is resized
Resize text 1.4.4 (AA)
Content overflows when text is resized
Reflow 1.4.10 (AA)
Content overflows on small viewports
Non-text Contrast 1.4.11 (AA)
Watch band color button "Gleich ausprobieren" does not have strong enough color contrast
Non-text Contrast 1.4.11 (AA)
"Play" buttons for video pop-ups do not have strong enough color contrast
Non-text Contrast 1.4.11 (AA)
Icon not marked as decorative use weak color contrast
Keyboard 2.1.1 (A)
Footnote dialog window does not receive keyboard focus on open
Keyboard 2.1.1 (A)
Video player controls in dialog windows cannot be operated by keyboard
Keyboard 2.1.1 (A)
Anchor links ("Notfallknopf", "GPS Standorte", ...) do not set focus correctly
Keyboard 2.1.1 (A)
Collapsible in intro section "... funktioniert im Schulmodus so" not keyboard accessible
Pause, Stop, Hide 2.2.2 (A)
Animations of smartwatch images have no method to pause, stop, hide
Focus Order 2.4.3 (A)
User-activated dynamic content not in correct focus order
Link Purpose (In Context) 2.4.4 (A)
Link text "Anzeigen" in section "Zur Hilfe-Seite mit häufigen Fragen und Antworten" does not describe link purpose
Headings and Labels 2.4.6 (AA)
Heading structure not accurately describes content
Focus Not Obscured (Minimum) 2.4.11 (AA)
Dialog windows obscure focus of underlying elements
Target Size (Minimum) 2.5.8 (AA)
Interactive element does not meet minimum target size
Name, Role, Value 4.1.2 (A)
Interactive element does not use correct semantic HTML
Unrelated to Success Criteria / Best Practice
Table sets cursor "grab"
Accompanying Files
Observation Details

The actual main watch image is built-in as background image and has no appropriate text alternative.

Remediation Notes

Ensure, added image description via alt attribute accurately describes the image. Add relevant information of the image and keep out all information that is not part of the image. Ensure, not adding false information to the image description.

Provide purpose equivalent text alternative for all non-decorative images, especially for relevant images like the smartwatch image that is the main topic of the page.

Accompanying Files
Observation Details

Image(s) in section "Die GPS-Kinderuhr –so individuell wie Ihr Kind" do not have purpose equivalent text alternatives. Text alternatives used shown in screenshot.

Observations for these text alternatives:

  • "Armband" implies an image of only the wristband; visually communicated is the watch as a whole; the purpose of the "Armband" image is not to only show the wristband, making the text alternative non-equivalent to the image's purpose

  • "Digitale Anzeige" used for multiple different images; text alternatives must be as unique as the images' purpose. The same text alternative must only be used if the purpose of those images is the same as well

  • "Pfeil" graphic including text "Gleich ausprobieren" does not mention said text in text alternative; when informative text content is part of a graphic, it must be part of the text alternative as well

  • "Armband Faecher" does not explain what "Fächer" means

Remediation Notes

Provide purpose equivalent text alternative for all non-decorative images, especially for relevant images like the smartwatch image that is the main topic of the page.

Ensure, understanding the purpose of the images to provide accurate, equivalent text alternatives. As a recommendation, replace the images in a layout with the image's purpose. What is the intention of using the image? When the intended purpose is final, use this as text alternative.

When referring to specific context, ensure, using the same wordings (Umrandung vs. Farbe der Uhr vs. Uhrrahmen).

Accompanying Files
Observation Details

Images use text alternative

  • "Empfehlervideo"

  • "Video Beispiel vom SOS-Knopf in Aktion"

  • "Video Tutorial zum Download der Anio 6 App"

Image purpose is to show background image still of video.

Remediation Notes

The image's text alternative depends on the intended purpose.

  • If the purpose is to show a video still, ensure, added image description via alt attribute accurately describes the image. Add relevant information of the image and keep out all information that is not part of the image. Ensure, not adding false information to the image description.

  • If the purpose is to function as the play button, describe the function as "Video XYZ abspielen"

  • If the image is decorative, provide null alt attribute

Accompanying Files
Observation Details

Image uses text alternative "Kids Watch Anio im Schulmodus und daneben Smartphone mit geöffneter Anio App"

  • Text alternative used twice on two different images.

  • Text alternative does not match content of "background" image (two girls, wearing watch)

Remediation Notes

Ensure, no text alternative is used twice. As with images, there rarely is a reason to show multiple images that give the exact same information and are meant to convey the exact same purpose. As the text alternative must be able to replace the image, same goes for the text alternative.

Accompanying Files
Observation Details

Store icons are used as functional images for store links. Being functional images, the image's purpose is to describe the function of the link rather than the contents of the image itself.

The icons use text alternatives:

  • Icon des Apple App Store

  • Icon des Google Play Store

Remediation Notes

Ensure, functional images are using a text alternative that describes the function, rather than the image content. Use

  • "Für Apple iPhone die Xplora App im App Store herunterladen" and

  • "Für Android Handys die Xplora App bei Google Play herunterladen"

Accompanying Files
Observation Details

Decorative icons must not have an accessible text alternative set. The decorative icons in question use non-null alt attributes.

Remediation Notes

Ensure, all decorative icons use null alt attributes. Remove the accessible name from decorative images by setting alt="".

Accompanying Files
Observation Details

The checkmark and cross icons in data table "GPS-Kinderuhren im Vergleich: Anio 6 vs. XPLORA 6 Play eSIM" have no accessible text alternative set. As the icon's purpose is crucial to understanding the content, text alternatives must be present and accessible. The code structure for the icons is as follows:

<span class="...">
  <span class="..." aria-hidden="true">
    <svg
      xmlns="http://www.w3.org/2000/svg"
      width="64.001"
      height="64"
      viewBox="0 0 64 64"
      role="img"
      class="..."
      focusable="false"
    >
      <path fill="#262626" d="..."></path>
    </svg>
  </span>
</span>

Observations:

  • Icon parent uses aria-hidden="true"

  • Icon has no accessible name as it misses the <title> element

  • Icon uses focusable="false", which is not needed as SVGs are non-focusable elements

Remediation Notes

Ensure, the icons use purpose equivalent text alternatives. Text alternative wording is dependent on the table header column wording as well. Possible text alternatives could be "Ja" for checkmark icon and "Nein" for cross icon. Ensure, wording matches the wording of table header column.

Accompanying Files
Observation Details

The video "SOS-Knopf in Aktion" is classified as "video-only" as the audio track doe not provide any informative content. The video provides information via visually presented content that is not additionally provided in a non-visual way.

Remediation Notes

Visually presented information must be made accessible in a non-visual way as well. This media alternative can be provided as:

  • text version with equivalent content / information

  • alternative (or additional) audio track with equivalent content / information

Observation Details

The video "Was Eltern über die GPS-Kinderuhr Anio 6 sagen:" has informative content but does not provide captions.

Remediation Notes

Spoken word in video's audio must be transcribed and provided as captions for the video. Ideally, captions include speaker information and all informative content, provided in the video's audio, including informative sounds.

Alternatively to captions, a full text transcript can be provided, if this transcript is either in the immediate context of the video or linked to from a link in the immediate context.

Accompanying Files
Observation Details

The video "So verbinden Sie die GPS-Kinderuhr mit Ihrem Smartphone" has informative content but does not provide captions.

Remediation Notes

Spoken word in video's audio must be transcribed and provided as captions for the video. Ideally, captions include speaker information and all informative content, provided in the video's audio, including informative sounds.

Alternatively to captions, a full text transcript can be provided, if this transcript is either in the immediate context of the video or linked to from a link in the immediate context.

Accompanying Files
Observation Details

Video "Was Eltern über die GPS-Kinderuhr Anio 6 sagen" provides visual information but has no audio description available.

Some information provided only visually:

  • "deutscher Server und App Made in Germany" & "Mehr Freiheit bei gleicher Sicherheit dank SOS" (timestamp: 0:33)

Remediation Notes

Ensure, all visually provided information in video content is also provided in the same video's audio content and / or a full-text alternative version.

If visually provided information is limited as it is in the given video, a more viable remediation option would be to remove this information from the video, so that the video does not provide more information than the audio.

Important side note: Choosing full-text alternative as remediation option does not mean to provide text alternative for parts of the visual content (i.e. for the few issues found in the observation notes). The criterion does not allow "mix-and-match" of audio description and text alternative.

Accompanying Files
Observation Details

Heading structure as per code markup:

h1 Was ist das Besondere an der Anio Kinderuhr mit GPS?
  h2 Für mehr Sicherheit und Selbständigkeit
  h2 Die GPS-Kinderuhr – so individuell wie Ihr Kind
  h2 Was Eltern über die GPS-Kinderuhr Anio 6 sagen
  h2 Die Kinderuhr mit GPS
  h2 SOS-Knopf der Kinderuhr mit GPS
  h2 Sichere Bereiche festlegen
  h2 Schulmodus bei der Kinderuhr mit GPS
  h2 Datenschutz
  h2 Schrittzähler
  h2 Lern-Ziffernblatt
  h2 Kinderuhr mit GPS Anio 6: So einfach geht's
  h2 Kinderuhr mit GPS Anio 6:So einfach geht's
  h2 Kinderuhr mit GPS Anio 6 - Technische Daten
    h3 Wasserbeständig
    h3 Akkulaufzeit
    h3 Speicher
    h3 Geeignet für
    h3 SOS-Taste
    h3 Funktioniert in
    h3 Gewicht
    h3 Abmessungen (mm)
  h2 GPS-Kinderuhren im Vergleich: Anio 6 vs. XPLORA 6 Play eSIM
  h2 Vergleich der technischen Daten von Anio 6 und XPLORA X6 Play eSIM
  h2 Fragen & Antworten zur GPS-Kinderuhr Anio 6
  h2 Smartphones
  h2 Tarife
  h2 Themen

Observations for this heading structure:

  • Heading structure main heading "Was ist das Besondere an der Anio Kinderuhr mit GPS?" & "Für mehr Sicherheit und Selbständigkeit" does not match visual presentation

  • Main heading implies all content on page is about "Besonderheiten" of Anio watch

  • "Für mehr Sicherheit und Selbstständigkeit" does not accurately describes its following content

  • Most headings level 2 add an "eyebrow" / "topline" above the heading; visual presentation implies a connection of heading and eyebrow, while markup adds eyebrow to the preceding heading every time, removing the implied connection

  • Heading "Kinderuhr mit GPS Anio 6: So einfach geht's" is duplicated in code

  • Content in section "Technische Daten" uses headings level 3 while being displayed as list content

  • "Direkteinstiege" headings are on level 2, instead of being grouped by "Direkteinstiege"

  • FAQ items do not show as headings

Remediation Notes
  • Ensure correct use of semantic HTML elements.

  • Use HTML headings for heading content only and match heading level hierarchy with visual presentation.

  • Use list elements (in this case, ideally a description list) for list content, instead of using headings with just few words of content

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

Observation Details

What is arguably list content, is not using semantic list elements. See

  • content in "Technische Daten" (using heading structure right now)

Remediation Notes

Use semantic list for all list content. The "technische Daten" content can ideally be displayed in an HTML description list <dl>.

<dl>
  <div>
    <dt>Wasserbeständigkeit</dt>
    <dd>IP 68</dd>
  </div>
  <div>
    <dt>SOS-Taste</dt>
    <dd>...</dd>
  </div>

  ...
</dl>
Accompanying Files
Observation Details

Navigating by assistive technology, focus order moves from main heading to green badge, resulting in the following announcement:

Was ist das Besondere an der Anio Kinderuhr mit GPS?

30 Jahre

Remediation Notes

Ensure, all content is in order of implied meaning. Especially elements with CSS position: absolute are prone to be in the "wrong" order.

The "30 Jahre" Badge is not in intended order and without any context may confuse users of assistive technology.

Accompanying Files
Observation Details

Decorative icon in background in section "Schulmodus bei der Kinderuhr mit GPS" is not marked as decorative and as such can be navigated to via assistive technology like screen readers. While not marked decorative, color contrast minimum shall be met. Color contrast of icons is below minimum (1.2:1 < 3:1).

Remediation Notes

I marked this issue priority 4 – Minor, as the icon most likely was intended to be used decoratively, like the other icons.

By marking decorative icons correctly as decorative, this issue can be remediated. See observation for 1.1.1 Non-text Content.

If the icons should remain marked non-decorative, ensure enough color contrast of the icon to the background color.

Accompanying Files
Observation Details

Colored circles are used as interactive elements to choose watch band color in the watch graphic. Color green (#9FBF54) does not have high enough color contrast ratio against the white background (2.1:1). A color contrast minimum of 3:1 must be met for all interactive elements, including buttons.

Remediation Notes

Ensure high enough color contrast of all interactive elements. In case of the color choice buttons, the possible remediation steps would be to

  • choose background color to meet contrast ratio minimum, or

  • use outline for buttons that does meet contrast ratio minimum

Side note: the buttons do have visible focus outlines when navigated to by keyboard. Ensure, when setting a button outline for the default un-focused and un-selected state, the color contrast ratio minimum is also met between un-focused and focused state, to not run into failure of 2.4.7 Focus Visible.

Accompanying Files
Observation Details

The play buttons in video pop-up thumbnails are used as interactive elements to start the video playback. Their colors do not have high enough color contrast ratio against the colored background. A color contrast minimum of 3:1 must be met for all interactive elements, including buttons. The contrast ratio should be met for the whole interactive element as well.

Remediation Notes

Ensure high enough color contrast of all interactive elements. In case of the video play buttons, the possible remediation could be to make the button non-transparent and add a different color outer outline. The so-called "oreo-outline" ensures visibility on both light and dark backgrounds:

outline: 1px solid white;
box-shadow: 0 0 0 3px black;
background-color: white;

Side note: the buttons do have visible focus outlines when navigated to by keyboard. Ensure, when setting a button outline for the default un-focused and un-selected state, the color contrast ratio minimum is also met between un-focused and focused state, to not run into failure of 2.4.7 Focus Visible.

Observation Details

When opening a footnote dialog window, the keyboard focus is not set to said dialog window. This leads to multiple issues:

  • The contents of the dialog window are not accessible via keyboard.

  • The dialog window can not be closed with the 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.

  • Since keyboard navigation stays possible, opening multiple dialog windows above each other also is possible.

Remediation Notes

Opening a dialog window with the keyboard must set the focus into the dialog window. Preferably onto the close button as the first interactive element in the dialog window. The focus must also be trapped inside the dialog window so the underlying page cannot be reached by keyboard while the dialog window is opened.

A better approach would be to use a <dialog> element for dialog windows.

Accompanying Files
Observation Details

Anchor links for on-page navigation are built using HTML button elements. Operating the link by keyboard, scrolls the page to the intended heading / section but does not move the focus. The focus stays on the link.

Remediation Notes

On-page navigation is done by links. To create a link, ensure using the semantic HTML link element <a> with a valid href attribute, referencing the id attribute's value of the intended target element.

  • <a href="#SosTasteSection">Notfallknopf</a>

  • <a href="#GpsTrackingSection">GPS Standorte</a>

  • <a href="#Uhrzeitlernen">Uhrzeitlernen</a>

  • <a href="#Schulmodus">Schulmodus</a>

Side note: When remediating this issue, please also ensure correct order of navigation elements to match content order and optionally using a semantic navigation element <nav> for the navigation list.

Observation Details

The video player in dialog windows cannot be operated by keyboard. The dialog window can be opened and closed by keyboard but the video player controls are not accessible via keyboard navigation.

Keyboard focus is trapped (also see 2.1.2 No Keyboard Trap) on close button.

Remediation Notes

Ensure keyboard accessibility of all interactive elements.

Accompanying Files
Observation Details

The collapsible (caret icon) in intro section "Das Besondere an der Anio 6 ist die Reduktion auf das Wesentliche:" can be expanded via keyboard navigation. Expanding the item should keep the focus on the same element so that a second click would collapse the item again.

Remediation Notes

Ensure keyboard accessibility by using semantic HTML elements, fitting the intended functionality. For a collapsible item, use the native dialog and summary elements and markup the code as follows (example structure):

<details>
  <summary>
    ...
  </summary>

  <ul>
    <li>...</li>
    <...
  </ul>
</details>
Observation Details

All animations longer than 5 seconds must have a method to pause, stop, hide them. The animations of the smartwatch images have no such method.

Remediation Notes

Ensure, all animations can be paused, stopped, hidden, or they are reduced to <5 seconds of movement.

Side note: Also ensure to respect user preferences for prefers-reduced-motion and either hide animations completely or reduce them.

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

Footnote dialog window is not keyboard accessible.


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

Link text "Anzeigen" does not provide link purpose on its own. As the link is not part of an HTML paragraph element, the link does not have immediate text context. Also, the previous paragraph does only add "Zur Hilfe-Seite mit häufigen Fragen und Antworten" to the context. While the parent heading is "Kinderuhr mit GPS Anio 6: So einfach geht's" and could help, identifying link purpose, the heading is not close enough to be count as context for purpose of this success criterion.

Remediation Notes

Use link text to describe link purpose or provide link purpose in immediate context. A purposeful link text could be "Die häufigsten Fragen und Antworten zur Kinderuhr mit GPS Anio 6 anzeigen".

Side note: The "info box" content could also be improved further by consolidating all tutorials, "Anleitungen", "Erklärvideos", "Hinweise", etc. into one help section like:

(download buttons)

  1. SIM-Karte in Uhr einlegen (PIN der SIM-Karte muss deaktiviert sein. Wenn Sie die SIM-Karte bei uns angefordert haben, ist dies bereits voreingestellt.)

  2. Anio App installieren
    (download buttons)

  3. QR-Code auf dem Display der Uhr scannen und die Uhr mit dem Smartphone koppeln. Fertig!

Hier können Sie sich ein Erklärvideo zur Einrichtung der Uhr anschauen oder sich die häufigsten Fragen und Antworten zur Anio 6 anzeigen lassen.

Ensure, the "Erklärvideo" uses a button element, when opening in a dialog window.

Observation Details

Heading structure as per code markup:

h1 Was ist das Besondere an der Anio Kinderuhr mit GPS?
  h2 Für mehr Sicherheit und Selbständigkeit
  h2 Die GPS-Kinderuhr – so individuell wie Ihr Kind
  h2 Was Eltern über die GPS-Kinderuhr Anio 6 sagen
  h2 Die Kinderuhr mit GPS
  h2 SOS-Knopf der Kinderuhr mit GPS
  h2 Sichere Bereiche festlegen
  h2 Schulmodus bei der Kinderuhr mit GPS
  h2 Datenschutz
  h2 Schrittzähler
  h2 Lern-Ziffernblatt
  h2 Kinderuhr mit GPS Anio 6: So einfach geht's
  h2 Kinderuhr mit GPS Anio 6:So einfach geht's
  h2 Kinderuhr mit GPS Anio 6 - Technische Daten
    h3 Wasserbeständig
    h3 Akkulaufzeit
    h3 Speicher
    h3 Geeignet für
    h3 SOS-Taste
    h3 Funktioniert in
    h3 Gewicht
    h3 Abmessungen (mm)
  h2 GPS-Kinderuhren im Vergleich: Anio 6 vs. XPLORA 6 Play eSIM
  h2 Vergleich der technischen Daten von Anio 6 und XPLORA X6 Play eSIM
  h2 Fragen & Antworten zur GPS-Kinderuhr Anio 6
  h2 Smartphones
  h2 Tarife
  h2 Themen

Observations for this heading structure:

  • Main heading must describe topic / purpose of whole page. As "Was ist das Besondere an der Anio Kinderuhr mit GPS?" it asks for "Besonderheiten" of the watch instead, implying every <h2> will describe one "Besonderheit", which is not the case; this renders some if not many headings of level 2 "incorrect"

  • Technical data in "Technische Daten" use headings for simple list content; also arguably "Geeignet für" and "Funktioniert in" are not considered technical specifications

  • Some headings repeat the name of the watch (Kinderuhr mit GPS Anio 6: So einfach geht's, Kinderuhr mit GPS Anio 6:So einfach geht's, Kinderuhr mit GPS Anio 6 - Technische Daten); while repetition is not a failure of this success criterion:

    • exact duplication should always be avoided, as using the same heading implies the same purpose of following content

    • "Technische Daten" would suffice, if main heading of page accurately introduces the watch name

  • "Kinderuhr mit GPS Anio 6: So einfach geht's" does not describe content purpose; "So einfach geht's" – better "Einrichtung der Anio 6 mit dem Smartphone – kinderleicht"

  • The FAQ section does not use headings

Heading structure is the most used form of navigating web pages by users of assistive technology, making it crucial to accurately use headings that describe the topic / purpose of their following content.

Remediation Notes

Ensure, each heading accurately describes topic / purpose of the introduced content.

Observation Details

Footnote trigger (star icon) does not meet minimum target size.


Interactive elements must have a target size of at least 24×24px. Minimum target size is required also for single icon buttons, stand-alone interactive icons and links. When target size is smaller, it will make it difficult for people to reliably interact with the elements. This includes people with motor disabilities, people using devices like styluses, people in moving vehicles, and mobile users altogether. Especially considering its use inside other interactive elements (e.g. footnote in badge) or multiple small interactive elements next to each other (e.g. social icons in a list).

Remediation Notes

Ensure, all interactive elements' target size is at least 24×24px.

While this does not necessarily mean, e.g. an icon itself must be 24×24px, the clickable area around it counts as the target size, if there is no overlapping interactive element in that area. Ideally, the element's visual boundaries adhere to the minimum target size of 24×24px itself.

Observation Details

The data table with class ComparisonTable__wrapper___... sets CSS cursor: grab. The cursor change implies non-existent interactivity. If the cursor is changed to imply grabbing navigation on smaller viewports, the cursor change should only apply to viewports that actually use grabbing functionality.

Priority: Critical Significant Page: Kider Uhr GPS Oneshop Observation Permalink
Accompanying Files
Observation Details
  • Emphasis is solely conveyed by color (magenta)

  • <b> used for emphasis


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.

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

    • Emphasis of text content uses <strong> and <em>

Observation Details

Some text content is written in a way, assistive technology has problems to announce it correctly. I will list fixes for some issues in the remediation notes.

Remediation Notes
  • "SOS-Knopf" is announced "Schosch-Knopf" (same for SOS-Kontakte, SOS-...); removing the hyphen makes the screen reader announce it as intended → "SOS Knopf", "SOS ..."

  • "x" in "Abmessungen" or "Auflösung" (Technische Daten) – e.g. "45,2 x 14,9 mm" (multiple occurrences found) is announced as letter X; use appropriate multiply symbol → "45,2 × 14,9 mm"

  • Time frames "36-48 Stunden" (and other "X bis Y") – "bis" is not announced in default screen reader settings; use word "bis" ideally to ensure default settings announce it as well → "36 bis 48 Stunden"

Accompanying Files
Observation Details

The :visited link style in "Direkteinstiege" section makes visited links barely visible on magenta background color.

Remediation Notes

Ensure enough color contrast between text content and background. Color contrast minimum must be met for all text content in all states (default, visited, focus, hover, ...)

Accompanying Files
Observation Details

Content in section "SOS Knopf der Kinderuhr mit GPS" becomes unreadable on 200% text zoom, as the image used as video still background is scaling with the text zoom.

Remediation Notes

Images ideally do not overflow 100% width (img { max-width: 100%; }). In this case, this will fix the issue completely.

Observation Details

Content in section "SOS Knopf der Kinderuhr mit GPS" becomes unreadable on 200% text zoom, as the image used as video still background is scaling with the text zoom.

Remediation Notes

Images ideally do not overflow 100% width (img { max-width: 100%; }). In this case, this will fix the issue completely.

Accompanying Files
Observation Details

Content in section "SOS Knopf der Kinderuhr mit GPS" becomes unreadable on 320px viewport width, as the image used as video still background is scaling with the text zoom.

Remediation Notes

Images ideally do not overflow 100% width (img { max-width: 100%; }). In this case, this will fix the issue completely.

Accompanying Files
Observation Details

Links use <button> instead of semantic link element.


All interactive elements that do not use the correct 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 incorrect 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, only semantic link elements are used for link functionality. <button><a href="#...">

Please refer to observation 1.3.1 Info and Relationships – "Semantic HTML" for general remarks about the use of semantic HTML.