general
sufficient
Any technology that supports pointer input (e.g. supporting any or all of the following: mouse pointer, touch on touch screen or trackpad, stylus input, or laser pointer input).
The objective of this technique is to ensure that users who have difficulties performing path-based gestures can operate a content slider with a single click or tap. A content slider contains chunks of content in a row. Usually several chunks of content are hidden, only one chunk is visible at any time. Left and right horizontal swiping over the visible part of the slider brings adjacent hidden chunks of content into view. Providing controls (for example, arrow buttons) as alternative means of input allows advancing the slider with a simple click or tap, i.e., without necessitating swipe gestures.
On touch screen devices, author-supplied path-based gestures usually do not work when OS level assistive technologies (AT) like a built-in screenreader are turned on. This is because AT generally consumes a path-based gestures so they would not reach the authored content. For example, a horizontal swipe gesture over the content slider will not work as intended by the author, but move the screen reader focus to the next or previous element. Some gestures may work if the user operates "pass-through gestures" which are often unreliable as they may depend on factors of hardware, operating system, operating system "skin", operating system setting, or user agent.
This technique addresses gestures where support has been implemented by authors, not gestures provided by the user agent (such as horizontal swiping to move through the browser history or vertical swiping to scroll through page content) or the operating system (e.g., gestures to move between open apps, or call up contextual menus of assistive technologies when these are enabled).
For content sliders that respond to path-based gestures: