Skip to content
This repository has been archived by the owner on Jun 30, 2018. It is now read-only.

Concurrent input mechanisms to master, for survey #915

Merged
merged 6 commits into from May 15, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
13 changes: 5 additions & 8 deletions understanding/21/concurrent-input-mechanisms.html
Expand Up @@ -10,12 +10,9 @@ <h1>Understanding Concurrent Input Mechanisms</h1>
<section id="intent"> <section id="intent">
<h2>Intent</h2> <h2>Intent</h2>
<section id="benefits"> <section id="benefits">
<p>Users may employ a variety of input mechanisms when interacting with web content. These may be a combination of mechanisms such as a keyboard or keyboard-like interfaces and pointer devices like a mouse, stylus or touchscreen.</p> <p>The intent of this Success Criterion is to ensure that people can use and switch between different modes of input when interacting with web content. Users may employ a variety of input mechanisms when interacting with web content. These may be a combination of mechanisms such as a keyboard or keyboard-like interfaces and pointer devices like a mouse, stylus or touchscreen.</p>
<p>Even though a device may have a primary or preferred input mechanism, the user may choose to apply alternative mechanisms. For example, a primary mechanism is the touchscreen on mobile phones and tablets, while a paired mouse or external keyboard may be an alternative.</p> <p>Even though a device may have a primary input mechanism, the user may choose to employ alternative input mechanisms when interacting with the device. For example, the primary mechanism for mobile phones and tablets is the touchscreen. The user of these devices may choose to use a paired mouse or external keyboard as an alternative to using the touchscreen.</p>

<p>Users should be able to switch input mechanisms at any point should the user determine that certain tasks and interactions are more easily accomplished by using an alternative input mechanism. Content must not limit the user's interaction to any particular input mechanism unless the restriction is essential, or is required to ensure the security of the content or to respect user settings.</p>
<p>The SC neither mandates nor forbids content authors to support multiple modes of input to be used in combination. This SC does not restrict modes of input, and input modes would be dependent on the technology used.</p>

<p>Dynamically adding, removing or switching a particular input mechanism should be doable at any point by a user if certain tasks and interactions are easier to accomplish that way. Content must therefore not limit the user's interaction to any particular input mechanism unless the restriction is essential, or is required to ensure the security of the content or to respect user settings.</p>
<p>Note: A touch-typing web application, which teaches users how to touch-type on a keyboard and/or measures their proficiency and speed, would be an example of an essential limitation to a particular input mechanism. </p> <p>Note: A touch-typing web application, which teaches users how to touch-type on a keyboard and/or measures their proficiency and speed, would be an example of an essential limitation to a particular input mechanism. </p>
<h3>Benefits</h3> <h3>Benefits</h3>
<ul> <ul>
Expand All @@ -31,7 +28,7 @@ <h2>Examples</h2>
<li>A user with mobility impairment pairs a mouse and keyboard to her mobile phone with a touchscreen. The phone can thereafter be operated by those input devices and the content does not accept the touchscreen as the only input mechanism.</li> <li>A user with mobility impairment pairs a mouse and keyboard to her mobile phone with a touchscreen. The phone can thereafter be operated by those input devices and the content does not accept the touchscreen as the only input mechanism.</li>
<li>On a touch-enabled laptop with coarse precision, people who have difficulty activating a small target because of hand tremors, limited dexterity or other reasons are still able to interact with content using their keyboard and trackpad.</li> <li>On a touch-enabled laptop with coarse precision, people who have difficulty activating a small target because of hand tremors, limited dexterity or other reasons are still able to interact with content using their keyboard and trackpad.</li>
<li>A user starts interacting with a page using a desktop keyboard, and then attaches a secondary touch-enabled monitor. Content can be operated using this newly added input mechanism and does not assume that the keyboard, the first input mechanism it detected, is the only one in use.</li> <li>A user starts interacting with a page using a desktop keyboard, and then attaches a secondary touch-enabled monitor. Content can be operated using this newly added input mechanism and does not assume that the keyboard, the first input mechanism it detected, is the only one in use.</li>
<li>A speech input user navigates content using voice commands which translate to simulated keyboard commands. When talking with a colleague, however, the user switches speech recognition off and uses the mouse instead.</li> <li>A speech input user navigates content using voice commands which translate to simulate mouse (and keyboard) commands. When talking with a colleague, however, the user turns speech recognition off and uses the mouse instead.</li>


</ul> </ul>
</section> </section>
Expand All @@ -57,7 +54,7 @@ <h3>Sufficient</h3>
<section id="failure"> <section id="failure">
<h2>Failure</h2> <h2>Failure</h2>
<ul> <ul>
<li>Registering <em>either</em> touch event handlers <em>or</em> keyboard/mouse event handlers based on a feature check/presence of a touchscreen in Javascript.</li> <li>Restricting event handlers based on the presence of a detected input mechanism.</li>
<li>Using CSS Media Queries Level 4 Interaction Media Features to determine what the UA deems to be the "primary" input mechanism and assuming no other input mechanisms are present/may be added/may be used.</li> <li>Using CSS Media Queries Level 4 Interaction Media Features to determine what the UA deems to be the "primary" input mechanism and assuming no other input mechanisms are present/may be added/may be used.</li>
</ul> </ul>
</section> </section>
Expand Down