Aktionen (1 issues)

Text cannot be doubled in font-size

Alle Geräte (1 issues)

Resizing text leaves very limited space in "Tarif ändern" dialog window

Apple iPad Air 11 2025 (1 issues)

Resizing text leaves very limited space

Daten Tarife (1 issues)

Vertical space with visible fixed footer with zoomed text limited

Kider Uhr GPS Oneshop (2 issues)

Content overflows when text is resized
Content overflows when text is resized

Magenta TV Streaming Dienste Partner DAZN (1 issues)

League collapsible content area not resizing with text size

Mobile Router (1 issues)

Resizing text leaves very limited space in "Tarif ändern" dialog window

Mobilfunk Netzausbau (1 issues)

Map not accessible with enlarged text

Prepaid Tarife (1 issues)

Text cannot be doubled in font-size

Smartphone Tarife (2 issues)

Resizing text leaves very limited space in tariff carousel
Tooltips in tariff chooser carousel not accessible when text is resized

Smartphones (1 issues)

Resizing text leaves very limited space in "Tarif ändern" dialog window

Smartwatches (1 issues)

Resizing text leaves very limited space in "Tarif ändern" dialog window

Sonim XP100 (1 issues)

Resizing text leaves very limited space
Resizing text leaves very limited space in "Tarif ändern" dialog window

Tastenhandys (1 issues)

Resizing text leaves very limited space in "Tarif ändern" dialog window

Travel Mobil Optionen (1 issues)

Text content needs two-dimensional scrolling when text is enlarged

Xiaomi 15 (1 issues)

Resizing text leaves very limited space
Observation Details

Text elements use px values for font-size, making it impossible to resize text to 200%.

E.g. the heading "Mehr Datenvolumen, gleicher Preis" starts with a font size of 43px (Viewport 1024×768px, Zoom 100%) and even gets smaller on larger viewports.

Remediation Notes

Text content must not use fixed px values for font sizes. Instead, use relative units (rem, em) to set font sizes.

Even better, evaluate the use of a responsive fluid type scale. More information about fluid type scales can be found at utopia.fyi.

Priority: Moderate High Page: Aktionen Observation Permalink
Observation Details

Text elements use px values for font-size, making it impossible to resize text to 200%.

Remediation Notes

Text content must not use fixed px values for font sizes. Instead, use relative units (rem, em) to set font sizes.

Even better, evaluate the use of a responsive fluid type scale. More information about fluid type scales can be found at utopia.fyi.

Priority: Serious Medium Page: Alle Geräte Observation Permalink
Accompanying Files
Observation Details

On base viewport size of 1024×768px and page zoom of 200%, the available:

  • vertical space in the "Tarif ändern" dialog window, due to fixed top and bottom bars, is less than 400px.

  • horizontal space, due to page zoom, is limited and cuts of hover tooltips

All content must be presented without loss of information or functionality.

Remediation Notes

The contents of the tooltip must stay accessible on smaller viewports. Ensure to display the contents within the boundaries of the viewport.

As the site is already working with dialog windows and collapsible elements, the easiest way to achieve this is to eliminate the tooltip functionality, as they (tooltip, dialog window, collapsible) serve the same purpose of hiding information. For this, the other used method must meet all success criteria, but this would eliminate the need of meeting them with yet another mechanism.

Hiding information from the user never is good user experience but the use of dialog windows or collapsible elements is widespread. While the use is no clear failure of accessibility criteria, concerning WCAG, one could argue it being at least a grey area for 3.2.4 Consistent Identification: "Components that have the same functionality within a set of Web pages are identified consistently." – this audit will not add this as a failure but asks to evaluate the use of multiple components that have the same purpose. Ideally, the functionality "hide from user" has a single way to be done. Splitting into a trigger being "block level" (FAQ) and "inline level" (Footnotes) seems reasonable, but adding another mechanism does not seem necessary.


While not a failure for the given success criterion, I also attached a screenshot showing the limited vertical space in the dialog window, which makes navigating the dialog's contents extremely difficult. Evaluation of the need for the top bar and the large bottom bar should be done.

Accompanying Files
Observation Details

Resizing text to 200% lets content overflow in league collapsible content areas.

Remediation Notes

Ensure, no container that has text content is fixed size, so that changing page or text zoom will correctly resize the container as well.

Observation Details

The interactive map is not accessible on when page zoom is set to 200 %. The contents do not reflow responsively, so certain functionality cannot be reached.

Priority: Serious Medium Page: Mobile Router Observation Permalink
Accompanying Files
Observation Details

On base viewport size of 1024×768px and page zoom of 200%, the available:

  • vertical space in the "Tarif ändern" dialog window, due to fixed top and bottom bars, is less than 400px.

  • horizontal space, due to page zoom, is limited and cuts of hover tooltips

All content must be presented without loss of information or functionality.

Remediation Notes

The contents of the tooltip must stay accessible on smaller viewports. Ensure to display the contents within the boundaries of the viewport.

As the site is already working with dialog windows and collapsible elements, the easiest way to achieve this is to eliminate the tooltip functionality, as they (tooltip, dialog window, collapsible) serve the same purpose of hiding information. For this, the other used method must meet all success criteria, but this would eliminate the need of meeting them with yet another mechanism.

Hiding information from the user never is good user experience but the use of dialog windows or collapsible elements is widespread. While the use is no clear failure of accessibility criteria, concerning WCAG, one could argue it being at least a grey area for 3.2.4 Consistent Identification: "Components that have the same functionality within a set of Web pages are identified consistently." – this audit will not add this as a failure but asks to evaluate the use of multiple components that have the same purpose. Ideally, the functionality "hide from user" has a single way to be done. Splitting into a trigger being "block level" (FAQ) and "inline level" (Footnotes) seems reasonable, but adding another mechanism does not seem necessary.


While not a failure for the given success criterion, I also attached a screenshot showing the limited vertical space in the dialog window, which makes navigating the dialog's contents extremely difficult. Evaluation of the need for the top bar and the large bottom bar should be done.

Priority: Serious Medium Page: Smartphones Observation Permalink
Accompanying Files
Observation Details

On base viewport size of 1024×768px and page zoom of 200%, the available:

  • vertical space in the "Tarif ändern" dialog window, due to fixed top and bottom bars, is less than 400px.

  • horizontal space, due to page zoom, is limited and cuts of hover tooltips

All content must be presented without loss of information or functionality.

Remediation Notes

The contents of the tooltip must stay accessible on smaller viewports. Ensure to display the contents within the boundaries of the viewport.

As the site is already working with dialog windows and collapsible elements, the easiest way to achieve this is to eliminate the tooltip functionality, as they (tooltip, dialog window, collapsible) serve the same purpose of hiding information. For this, the other used method must meet all success criteria, but this would eliminate the need of meeting them with yet another mechanism.

Hiding information from the user never is good user experience but the use of dialog windows or collapsible elements is widespread. While the use is no clear failure of accessibility criteria, concerning WCAG, one could argue it being at least a grey area for 3.2.4 Consistent Identification: "Components that have the same functionality within a set of Web pages are identified consistently." – this audit will not add this as a failure but asks to evaluate the use of multiple components that have the same purpose. Ideally, the functionality "hide from user" has a single way to be done. Splitting into a trigger being "block level" (FAQ) and "inline level" (Footnotes) seems reasonable, but adding another mechanism does not seem necessary.


While not a failure for the given success criterion, I also attached a screenshot showing the limited vertical space in the dialog window, which makes navigating the dialog's contents extremely difficult. Evaluation of the need for the top bar and the large bottom bar should be done.

Priority: Serious Medium Page: Smartwatches Observation Permalink
Accompanying Files
Observation Details

On base viewport size of 1024×768px and page zoom of 200%, the available:

  • vertical space in the "Tarif ändern" dialog window, due to fixed top and bottom bars, is less than 400px.

  • horizontal space, due to page zoom, is limited and cuts of hover tooltips

All content must be presented without loss of information or functionality.

Remediation Notes

The contents of the tooltip must stay accessible on smaller viewports. Ensure to display the contents within the boundaries of the viewport.

As the site is already working with dialog windows and collapsible elements, the easiest way to achieve this is to eliminate the tooltip functionality, as they (tooltip, dialog window, collapsible) serve the same purpose of hiding information. For this, the other used method must meet all success criteria, but this would eliminate the need of meeting them with yet another mechanism.

Hiding information from the user never is good user experience but the use of dialog windows or collapsible elements is widespread. While the use is no clear failure of accessibility criteria, concerning WCAG, one could argue it being at least a grey area for 3.2.4 Consistent Identification: "Components that have the same functionality within a set of Web pages are identified consistently." – this audit will not add this as a failure but asks to evaluate the use of multiple components that have the same purpose. Ideally, the functionality "hide from user" has a single way to be done. Splitting into a trigger being "block level" (FAQ) and "inline level" (Footnotes) seems reasonable, but adding another mechanism does not seem necessary.


While not a failure for the given success criterion, I also attached a screenshot showing the limited vertical space in the dialog window, which makes navigating the dialog's contents extremely difficult. Evaluation of the need for the top bar and the large bottom bar should be done.

Priority: Serious Medium Page: Tastenhandys Observation Permalink
Accompanying Files
Observation Details

On base viewport size of 1024×768px and page zoom of 200%, the available:

  • vertical space in the "Tarif ändern" dialog window, due to fixed top and bottom bars, is less than 400px.

  • horizontal space, due to page zoom, is limited and cuts of hover tooltips

All content must be presented without loss of information or functionality.

Remediation Notes

The contents of the tooltip must stay accessible on smaller viewports. Ensure to display the contents within the boundaries of the viewport.

As the site is already working with dialog windows and collapsible elements, the easiest way to achieve this is to eliminate the tooltip functionality, as they (tooltip, dialog window, collapsible) serve the same purpose of hiding information. For this, the other used method must meet all success criteria, but this would eliminate the need of meeting them with yet another mechanism.

Hiding information from the user never is good user experience but the use of dialog windows or collapsible elements is widespread. While the use is no clear failure of accessibility criteria, concerning WCAG, one could argue it being at least a grey area for 3.2.4 Consistent Identification: "Components that have the same functionality within a set of Web pages are identified consistently." – this audit will not add this as a failure but asks to evaluate the use of multiple components that have the same purpose. Ideally, the functionality "hide from user" has a single way to be done. Splitting into a trigger being "block level" (FAQ) and "inline level" (Footnotes) seems reasonable, but adding another mechanism does not seem necessary.


While not a failure for the given success criterion, I also attached a screenshot showing the limited vertical space in the dialog window, which makes navigating the dialog's contents extremely difficult. Evaluation of the need for the top bar and the large bottom bar should be done.

Priority: Serious Medium Page: Tablets Observation Permalink
Accompanying Files
Observation Details

On base viewport size of 1024×768px and page zoom of 200%, the available:

  • vertical space in the "Tarif ändern" dialog window, due to fixed top and bottom bars, is less than 400px.

  • horizontal space, due to page zoom, is limited and cuts of hover tooltips

All content must be presented without loss of information or functionality.

Remediation Notes

The contents of the tooltip must stay accessible on smaller viewports. Ensure to display the contents within the boundaries of the viewport.

As the site is already working with dialog windows and collapsible elements, the easiest way to achieve this is to eliminate the tooltip functionality, as they (tooltip, dialog window, collapsible) serve the same purpose of hiding information. For this, the other used method must meet all success criteria, but this would eliminate the need of meeting them with yet another mechanism.

Hiding information from the user never is good user experience but the use of dialog windows or collapsible elements is widespread. While the use is no clear failure of accessibility criteria, concerning WCAG, one could argue it being at least a grey area for 3.2.4 Consistent Identification: "Components that have the same functionality within a set of Web pages are identified consistently." – this audit will not add this as a failure but asks to evaluate the use of multiple components that have the same purpose. Ideally, the functionality "hide from user" has a single way to be done. Splitting into a trigger being "block level" (FAQ) and "inline level" (Footnotes) seems reasonable, but adding another mechanism does not seem necessary.


While not a failure for the given success criterion, I also attached a screenshot showing the limited vertical space in the dialog window, which makes navigating the dialog's contents extremely difficult. Evaluation of the need for the top bar and the large bottom bar should be done.

Priority: Moderate Medium Page: Daten Tarife Observation Permalink
Accompanying Files
Observation Details

On base viewport size of 1036×768px, page zoom of 200%, the available vertical space, due to fixed bottom bars, is just ~400px.

Remediation Notes

While not a failure for the given success criterion, the limited vertical space makes navigating the content very difficult. Evaluation of the need for the large fixed bottom bar should be done.

The fixed bottom bar could e.g. be shrunken by

  • decreasing margins and/or paddings,

  • decreasing the size of the primary button(s),

  • changing the layout to display price information and primary button side-by-side.

  • evaluating use of a smaller bar that shows more information in a collapsible

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

On base viewport size of 1024×768px and page zoom of 200%, the available:

  • vertical space in the tariff carousel, is 400px.

  • horizontal space, due to page zoom, is limited and cuts of hover tooltips

All content must be presented without loss of information or functionality.

Remediation Notes

The contents of the tooltip must stay accessible on smaller viewports. Ensure to display the contents within the boundaries of the viewport.

Accompanying Files
Observation Details

On base viewport size of 1024×768px and page zoom of 200%, the available:

  • vertical space on the page after "Preisübersicht" is sticky < 400px

  • vertical space in the tariff carousel < 400px.

  • horizontal space, due to page zoom, is limited and cuts of hover tooltips

All content must be presented without loss of information or functionality.

Remediation Notes

Priority: Serious Medium Page: Xiaomi 15 Observation Permalink
Accompanying Files
Observation Details

On base viewport size of 1024×768px and page zoom of 200%, the available:

  • vertical space on the page after "Preisübersicht" is sticky < 400px

  • vertical space in the tariff carousel < 400px.

  • horizontal space, due to page zoom, is limited and cuts of hover tooltips

All content must be presented without loss of information or functionality.

Remediation Notes

Accompanying Files
Observation Details

Text content in dialog window "Länderliste" does not properly reflow and needs two-dimensional scrolling to access all content.

Remediation Notes

Ensure, all content properly reflows with text enlarged to 200%.

Priority: Serious Medium Page: Sonim XP100 Observation Permalink
Accompanying Files
Observation Details

On base viewport size of 1024×768px and page zoom of 200%, the available:

  • vertical space on the page after "Preisübersicht" is sticky < 400px

  • vertical space in the tariff carousel < 400px. ("Tarif ändern" dialog window)

  • horizontal space, due to page zoom, is limited and cuts of hover tooltips ("Tarif ändern" dialog window)

All content must be presented without loss of information or functionality.

Remediation Notes