Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Understanding On Input (SC 3.2.2) #1017

Closed
wants to merge 5 commits into from
Closed

Update Understanding On Input (SC 3.2.2) #1017

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
8e8ec22
Update on-input.html
Jan 26, 2020
30e2bcc
Merge branch 'main' into oninput
patrickhlauke Nov 5, 2024
7977478
Merge branch 'main' into oninput
patrickhlauke Nov 29, 2024
fe27dde
Update on-input.html
stevefaulkner Feb 21, 2025
8010ad1
Merge branch 'main' into oninput
patrickhlauke Feb 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
161 changes: 37 additions & 124 deletions understanding/20/on-input.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,21 +7,16 @@
</head>
<body>
<h1>Understanding On Input</h1>

<section id="brief">
<h2>In brief</h2>
<dl>
<dt>Goal</dt><dd>Content can be operated more predictably.</dd>
<dt>What to do</dt><dd>Forewarn users if their context will change based on their input.</dd>
<dt>Why it's important</dt><dd>Content that behaves predictably is especially important to people with disabilities.</dd>
</dl>

</section>

<section id="intent">
<h2>Intent of On Input</h2>


<p>The intent of this Success Criterion is to ensure that entering data or selecting
a form control has predictable effects. Changing the setting of any user interface
component is changing some aspect in the control that will persist when the user is
Expand All @@ -30,77 +25,58 @@ <h2>Intent of On Input</h2>
a link or a button does not. Changes in context can confuse users who do not easily
perceive the change or are easily distracted by changes. Changes of context are appropriate
only when it is clear that such a change will happen in response to the user's action.


</p>

<div class="note">

<p>This Success Criterion covers changes in context due to changing the setting of a
control. Clicking on links or buttons is activating a control, not
changing the setting of that control.
</p>

</p>
</div>

<div class="note">

<div class="note">
<p>What is meant by "component" and "user interface component" here is also sometimes
called "user interface element".
</p>

</div>


<div class="note">
<p>If the user interface component is not fully operable with the keyboard due to the <a class="glossary">change of context</a>,
this would be a failure of SC 2.1.1.
</p>
</div>
<div class="note">
<p>A <a class="glossary">change of context</a> should only be made if this makes further operation of the application easier.
If the change of context makes the operation difficult for disabled people, it is recommended to avoid the context change.
</p>
</div>
</section>
<section id="benefits">
<h2>Benefits of On Input</h2>


<ul>

<ul>
<li>This Success Criterion helps users with disabilities by making interactive content
more predictable. Unexpected changes of context can be so disorienting for users with
visual disabilities or cognitive limitations that they are unable to use the content.


visual disabilities or cognitive limitations that they are unable to use the content.
</li>

<li>

<p>Individuals who are unable to detect changes of context are less likely to become
disoriented while navigating a site. For example:

</p>

<ul>

disoriented while navigating a site. For example:
</p>
<ul>
<li>Individuals who are blind or have low vision may have difficulty knowing when a visual
context change has occurred, such as a new window popping up. In this case, warning
users of context changes in advance minimizes confusion when the user discovers that
the back button no longer behaves as expected.

the back button no longer behaves as expected.
</li>

</ul>

</ul>
</li>

<li>Some individuals with low vision, with reading and intellectual disabilities, and
others who have difficulty interpreting visual cues may benefit from additional cues
in order to detect changes of context.
</li>

</ul>

</section>

<section id="examples">
<h2>Examples of On Input</h2>


<ul>

<ul>
<li>
A form is provided for creating calendar entries in a Web based calendaring and scheduling
application. Along with the standard fields for subject, time and location, there
Expand All @@ -109,140 +85,77 @@ <h2>Examples of On Input</h2>
for meeting, additional fields are displayed on the page for entering the meeting
participants. Different fields appear if the reminder button is chosen. Because only
parts of the entry change and the overall structure remains the same the basic context
remains for the user.

</li>

remains for the user. </li>
<li>
A form contains fields representing US phone numbers. All of the numbers have a three
digit area code followed by a three digit prefix and finally a four digit number,
and each part of the phone number is entered into a separate field. When the user
completes the entry of one field the focus automatically moves to the next field of
the phone number. This behavior of phone fields is described for the user at the beginning
of the form.

</li>

of the form.</li>
</ul>

</section>

<section id="resources">
<h2>Resources for On Input</h2>


<h2>Resources for On Input</h2>
</section>

<section id="techniques">
<h2>Techniques for On Input</h2>


<section id="sufficient">
<h3>Sufficient Techniques for On Input</h3>


<ul>

<ul>
<li>

<p>

<a href="../Techniques/general/G80" class="general">Providing a submit button to initiate a change of context</a> using a technology-specific technique listed below
</p>

<ul>

<li>

<a href="../Techniques/html/H32" class="html">Providing submit buttons</a>

<a href="../Techniques/html/H32" class="html">Providing submit buttons</a>
</li>

<li>

<a href="../Techniques/html/H84" class="html">Using a button with a select element to perform an action</a>

<li>
<a href="../Techniques/html/H84" class="html">Using a button with a select element to perform an action</a>
</li>

<li>

<a href="../Techniques/pdf/PDF15" class="pdf"></a>

<a href="../Techniques/pdf/PDF15" class="pdf"></a>
</li>

</ul>

</li>

<li>

<a href="../Techniques/general/G13" class="general">Describing what will happen before a change to a form control is made</a>

<a href="../Techniques/general/G13" class="general">Describing what will happen before a change to a form control is made</a>
</li>

<li>

<a href="../Techniques/client-side-script/SCR19" class="script"></a>

<li>
<a href="../Techniques/client-side-script/SCR19" class="script"></a>
</li>

</ul>

<div class="note">

<div class="note">
<p>A change of content is not always a
<a class="glossary">change of context</a>. This success criterion is automatically met if changes in content are not also changes
of context.
</p>

</div>

</section>

<section id="advisory">
<h3>Additional Techniques (Advisory) for On Input</h3>


<ul>

<li>

<a href="../Techniques/general/G201" class="general">Giving users advanced warning when opening a new window</a>

<ul>
<li>
<a href="../Techniques/general/G201" class="general">Giving users advanced warning when opening a new window</a>
</li>

</ul>

</section>

<section id="failure">
<h3>Failures for On Input</h3>


<ul>

<li>

<a href="../Techniques/failures/F36" class="failure">Failure due to automatically submitting a form and presenting new content without
prior warning when the last field in the form is given a value
</a>

</li>

<li>

<a href="../Techniques/failures/F37" class="failure">Failure due to launching a new window without prior warning when the status of a radio
button, check box or select list is changed
</a>

</li>


</ul>

</section>

</ul>
</section>
</section>

</body>
</html>