Important Notice: This website shows interim results and does not represent a complete accessibility audit. The content is not final, is under heavy development, and is not legally binding. The website and all its content is for internal use only; unauthorized use or distribution may result in legal consequences.

Documentation of accessibility observations for Deutsche Telekom – Mobilfunk & OneShop

15 issues found for 2.5.1 Pointer Gestures

Alle Geräte (1 issues)

View All Issues for Page Visit Page
Manufacturer filter can only be operated by dragging motion on mobile

Handy Verkaufen (1 issues)

View All Issues for Page Visit Page
Manufacturer filter can only be operated by dragging motion on mobile

Magenta TV Streaming Dienste Partner DAZN (2 issues)

View All Issues for Page Visit Page
"Paket" tile slider not operable without dragging/scrolling
"Demnächst live" carousel has no pagination on desktop viewport

Mobile Router (1 issues)

View All Issues for Page Visit Page
Device Category links navigation can only be operated by dragging motion on mobile

Mobilfunk Netzausbau (2 issues)

View All Issues for Page Visit Page
Map navigation not accessible by single pointer events
Map navigation not accessible by single pointer events

Smartphones (2 issues)

View All Issues for Page Visit Page
Device Category links navigation can only be operated by dragging motion on mobile
Manufacturer filter can only be operated by dragging motion on mobile

Smartwatches (1 issues)

View All Issues for Page Visit Page
Device Category links navigation can only be operated by dragging motion on mobile

Tablets (2 issues)

View All Issues for Page Visit Page
Device Category links navigation can only be operated by dragging motion on mobile
Manufacturer filter can only be operated by dragging motion on mobile

Tarife (1 issues)

View All Issues for Page Visit Page
Content cards can only be operated by dragging motion on mobile

Tastenhandys (1 issues)

View All Issues for Page Visit Page
Device Category links navigation can only be operated by dragging motion on mobile

iPhone Erleben (1 issues)

View All Issues for Page Visit Page
Overflowing elements rely on pointer gesture to be navigated
Priority: Minor Low Page: Alle Geräte Observation Permalink
Accompanying Files
Observation Details

The manufacturer filter (direct filter buttons) can only be operated by horizontal scroll on desktop and by dragging movement on a mobile device. As the dragging needs a base precision to stop the movement at the right time to reach the wanted filter button, a single pointer alternative for operation / navigation must be offered.

The viewport of the example screenshot is 375×635px, simulating an Apple iPhone 11 Pro. While this is an old device and more current phones do tend to have increased viewport widths, this test would look even more drastic on the 320px viewport width, the WCAG sets for e.g. 1.4.10 Reflow.

As the manufacturer filter buttons are accessible within the filter options dialog window as well, the issue is rated priority "Minor" and the impact on accessibility conformance is low. However, usability / user experience is affected by this issue, as the user is not aware of those buttons being duplicated from the filter option dialog window.

Remediation Notes

Possible methods to remediate and to ensure access to the buttons:

  • Adding pagination (single pointer arrow buttons)

  • Reflow to multiple lines of buttons (also see 1.4.10 Reflow)

Note, that the WCAG, and success criterion 2.5.7 Dragging Movements specifically, do not require presentation / layout parity of different devices, viewports, etc. This means, while functionality and information parity is a must, the layout and presentation can be different.

This allows for another method to remediate, by only displaying the amount of buttons, fitting the available space. So while "all" buttons are shown on larger viewports, the number can decrease on smaller viewports, as long as the functionality parity is met, which is the case, with the filter buttons being accessible via the filter dialog window.

Positive side-effect of the latter option is one less mechanism (horizontally scrolling items) to be maintained.

Priority: Serious Low Page: Smartphones Observation Permalink
Observation Details

The device category links navigation can only be operated by horizontal scroll on desktop and by dragging movement on a mobile device. As the dragging needs a base precision to stop the movement at the right time to reach the wanted category link, a single pointer alternative for operation / navigation must be offered.

The viewport tested is 375×635px, simulating an Apple iPhone 11 Pro. While this is an old device and more current phones do tend to have increased viewport widths, this test would look even more drastic on the 320px viewport width, the WCAG sets for e.g. 1.4.10 Reflow.

Remediation Notes

Possible methods to remediate and to ensure access to the links:

  • Adding pagination (single pointer arrow buttons)

  • Reflow to multiple lines (also see 1.4.10 Reflow)

Note, that the WCAG, and success criterion 2.5.7 Dragging Movements specifically, do not require presentation / layout parity of different devices, viewports, etc. This means, while functionality and information parity is a must, the layout and presentation can be different.

Priority: Serious Low Page: Tarife Observation Permalink
Observation Details

The content cards can only be operated by horizontal scroll or by dragging movement on smaller viewports / mobile. As the dragging needs a base precision to stop the movement at the right time to reach the wanted content card, a single pointer alternative for operation / navigation must be offered.

Remediation Notes

Possible methods to remediate and to ensure access to the links:

  • Adding pagination (single pointer arrow buttons)

  • Reflow to multiple lines (also see 1.4.10 Reflow)

Note, that the WCAG, and success criterion 2.5.7 Dragging Movements specifically, do not require presentation / layout parity of different devices, viewports, etc. This means, while functionality and information parity is a must, the layout and presentation can be different.

Priority: Minor Low Page: Magenta TV Streaming Dienste Partner DAZN Observation Permalink
Observation Details

The carousel "demnächst live" does not show single pointer elements to navigate on desktop viewport while the cursor does change to a cursor: grab.

Remediation Notes

Ensure interactivity of carousel component is disabled when not needed.

Priority: Critical Low Page: Magenta TV Streaming Dienste Partner DAZN Observation Permalink
Accompanying Files
Observation Details

The slider for "Paket" tiles does overflow on the x axis on smaller viewports and requires scrolling / dragging movement to navigate. A single point navigation alternative like pagination or arrow buttons is not offered.

Remediation Notes

Ensure, not relying on dragging movements. A pagination option as single point alternative for navigation should be offered. Ideally ensure consistency of all carousel components in style and operability.

Priority: Serious Significant Page: Mobilfunk Netzausbau Observation Permalink
Observation Details

  • Map on mobile uses two-finger zooming, not displaying the zoom buttons from desktop view and not allowing zooming by single pointer, e.g. double tap, tap and hold, etc.

  • Map on mobile uses "swiping" for scrolling the map. No single pointer mechanism is available, e.g. arrow buttons

Remediation Notes

While one functionality of the map can still be accessed by entering address or coordinates, the functionality of overview, of moving freely within the map, etc. is not accessible. Ensure navigational buttons (zoom, scroll) are present and accessible and especially stay accessible on mobile viewports.

Priority: Serious Significant Page: Mobilfunk Netzausbau Observation Permalink
Observation Details

Map on mobile uses "swiping" for scrolling the map. No single pointer mechanism is available, e.g. arrow buttons

Remediation Notes

While one functionality of the map can still be accessed by entering address or coordinates, the functionality of overview, of moving freely within the map, etc. is not accessible. Ensure navigational buttons (zoom, scroll) are present and accessible and especially stay accessible on mobile viewports.

Priority: Serious Low Page: Mobile Router Observation Permalink
Observation Details

The device category links navigation can only be operated by horizontal scroll on desktop and by dragging movement on a mobile device. As the dragging needs a base precision to stop the movement at the right time to reach the wanted category link, a single pointer alternative for operation / navigation must be offered.

The viewport tested is 375×635px, simulating an Apple iPhone 11 Pro. While this is an old device and more current phones do tend to have increased viewport widths, this test would look even more drastic on the 320px viewport width, the WCAG sets for e.g. 1.4.10 Reflow.

Remediation Notes

Possible methods to remediate and to ensure access to the links:

  • Adding pagination (single pointer arrow buttons)

  • Reflow to multiple lines (also see 1.4.10 Reflow)

Note, that the WCAG, and success criterion 2.5.7 Dragging Movements specifically, do not require presentation / layout parity of different devices, viewports, etc. This means, while functionality and information parity is a must, the layout and presentation can be different.

Priority: Minor Low Page: Smartphones Observation Permalink
Accompanying Files
Observation Details

The manufacturer filter (direct filter buttons) can only be operated by horizontal scroll on desktop and by dragging movement on a mobile device. As the dragging needs a base precision to stop the movement at the right time to reach the wanted filter button, a single pointer alternative for operation / navigation must be offered.

The viewport of the example screenshot is 375×635px, simulating an Apple iPhone 11 Pro. While this is an old device and more current phones do tend to have increased viewport widths, this test would look even more drastic on the 320px viewport width, the WCAG sets for e.g. 1.4.10 Reflow.

As the manufacturer filter buttons are accessible within the filter options dialog window as well, the issue is rated priority "Minor" and the impact on accessibility conformance is low. However, usability / user experience is affected by this issue, as the user is not aware of those buttons being duplicated from the filter option dialog window.

Remediation Notes

Possible methods to remediate and to ensure access to the buttons:

  • Adding pagination (single pointer arrow buttons)

  • Reflow to multiple lines of buttons (also see 1.4.10 Reflow)

Note, that the WCAG, and success criterion 2.5.7 Dragging Movements specifically, do not require presentation / layout parity of different devices, viewports, etc. This means, while functionality and information parity is a must, the layout and presentation can be different.

This allows for another method to remediate, by only displaying the amount of buttons, fitting the available space. So while "all" buttons are shown on larger viewports, the number can decrease on smaller viewports, as long as the functionality parity is met, which is the case, with the filter buttons being accessible via the filter dialog window.

Positive side-effect of the latter option is one less mechanism (horizontally scrolling items) to be maintained.

Priority: Serious Low Page: Smartwatches Observation Permalink
Observation Details

The device category links navigation can only be operated by horizontal scroll on desktop and by dragging movement on a mobile device. As the dragging needs a base precision to stop the movement at the right time to reach the wanted category link, a single pointer alternative for operation / navigation must be offered.

The viewport tested is 375×635px, simulating an Apple iPhone 11 Pro. While this is an old device and more current phones do tend to have increased viewport widths, this test would look even more drastic on the 320px viewport width, the WCAG sets for e.g. 1.4.10 Reflow.

Remediation Notes

Possible methods to remediate and to ensure access to the links:

  • Adding pagination (single pointer arrow buttons)

  • Reflow to multiple lines (also see 1.4.10 Reflow)

Note, that the WCAG, and success criterion 2.5.7 Dragging Movements specifically, do not require presentation / layout parity of different devices, viewports, etc. This means, while functionality and information parity is a must, the layout and presentation can be different.

Priority: Serious Low Page: Tastenhandys Observation Permalink
Observation Details

The device category links navigation can only be operated by horizontal scroll on desktop and by dragging movement on a mobile device. As the dragging needs a base precision to stop the movement at the right time to reach the wanted category link, a single pointer alternative for operation / navigation must be offered.

The viewport tested is 375×635px, simulating an Apple iPhone 11 Pro. While this is an old device and more current phones do tend to have increased viewport widths, this test would look even more drastic on the 320px viewport width, the WCAG sets for e.g. 1.4.10 Reflow.

Remediation Notes

Possible methods to remediate and to ensure access to the links:

  • Adding pagination (single pointer arrow buttons)

  • Reflow to multiple lines (also see 1.4.10 Reflow)

Note, that the WCAG, and success criterion 2.5.7 Dragging Movements specifically, do not require presentation / layout parity of different devices, viewports, etc. This means, while functionality and information parity is a must, the layout and presentation can be different.

Priority: Serious Low Page: Tablets Observation Permalink
Observation Details

The device category links navigation can only be operated by horizontal scroll on desktop and by dragging movement on a mobile device. As the dragging needs a base precision to stop the movement at the right time to reach the wanted category link, a single pointer alternative for operation / navigation must be offered.

The viewport tested is 375×635px, simulating an Apple iPhone 11 Pro. While this is an old device and more current phones do tend to have increased viewport widths, this test would look even more drastic on the 320px viewport width, the WCAG sets for e.g. 1.4.10 Reflow.

Remediation Notes

Possible methods to remediate and to ensure access to the links:

  • Adding pagination (single pointer arrow buttons)

  • Reflow to multiple lines (also see 1.4.10 Reflow)

Note, that the WCAG, and success criterion 2.5.7 Dragging Movements specifically, do not require presentation / layout parity of different devices, viewports, etc. This means, while functionality and information parity is a must, the layout and presentation can be different.

Priority: Minor Low Page: Tablets Observation Permalink
Accompanying Files
Observation Details

The manufacturer filter (direct filter buttons) can only be operated by horizontal scroll on desktop and by dragging movement on a mobile device. As the dragging needs a base precision to stop the movement at the right time to reach the wanted filter button, a single pointer alternative for operation / navigation must be offered.

The viewport of the example screenshot is 375×635px, simulating an Apple iPhone 11 Pro. While this is an old device and more current phones do tend to have increased viewport widths, this test would look even more drastic on the 320px viewport width, the WCAG sets for e.g. 1.4.10 Reflow.

As the manufacturer filter buttons are accessible within the filter options dialog window as well, the issue is rated priority "Minor" and the impact on accessibility conformance is low. However, usability / user experience is affected by this issue, as the user is not aware of those buttons being duplicated from the filter option dialog window.

Remediation Notes

Possible methods to remediate and to ensure access to the buttons:

  • Adding pagination (single pointer arrow buttons)

  • Reflow to multiple lines of buttons (also see 1.4.10 Reflow)

Note, that the WCAG, and success criterion 2.5.7 Dragging Movements specifically, do not require presentation / layout parity of different devices, viewports, etc. This means, while functionality and information parity is a must, the layout and presentation can be different.

This allows for another method to remediate, by only displaying the amount of buttons, fitting the available space. So while "all" buttons are shown on larger viewports, the number can decrease on smaller viewports, as long as the functionality parity is met, which is the case, with the filter buttons being accessible via the filter dialog window.

Positive side-effect of the latter option is one less mechanism (horizontally scrolling items) to be maintained.

Priority: Critical Medium Page: iPhone Erleben Observation Permalink
Observation Details

When (non-native) functionality relies on non-single pointer gestures, like swiping sliders, table columns, or opening sidebars by swipe, these must also have a single pointer variant accessible. The situation may occur, when changing to smaller viewports and the component in question is set to not use native overflow methods and to not reflow.

Users, not able to use complex pointer gestures, will not be able to access the elements in question and most likely will have difficulties to access information that is overflowing the viewport.

The page uses carousels for all major content cards on smaller viewports, not implementing pagination/navigation buttons to navigate by single pointer.

Remediation Notes

Ideally, elements overflowing the viewport would reflow instead. This way, the elements can rely on the user-agents functionality, and additional functionality must not be implemented. Another option would be to allow native overflow with scroll. If not using native methods to address these. If no native method is used:

Ensure, no functionality solely relies on complex pointer gestures. E.g. when using swiping functionality to navigate through slider items or table columns, ensure additionally adding accessible single pointer methods with equal functionality.

  • Sliders should use navigation (e.g. left/right arrow) or buttons

  • Responsive table columns should use navigation (e.g. left/right arrow) or buttons

Priority: Critical Low Page: Handy Verkaufen Observation Permalink
Accompanying Files
Observation Details

The manufacturer filter (direct filter buttons in device carousel) can only be operated by horizontal scroll on desktop and by dragging movement on a mobile device. As the dragging needs a base precision to stop the movement at the right time to reach the wanted filter button, a single pointer alternative for operation / navigation must be offered.

The viewport of the example screenshot is 375×635px, simulating an Apple iPhone 11 Pro. While this is an old device and more current phones do tend to have increased viewport widths, this test would look even more drastic on the 320px viewport width, the WCAG sets for e.g. 1.4.10 Reflow.

Remediation Notes

Possible methods to remediate and to ensure access to the buttons:

  • Adding pagination (single pointer arrow buttons)

  • Reflow to multiple lines of buttons (also see 1.4.10 Reflow)