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.

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

Examples updates #1617

Merged
merged 3 commits into from Feb 9, 2021
Merged
Changes from 1 commit
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
9 changes: 4 additions & 5 deletions understanding/22/visible-controls.html
Expand Up @@ -58,7 +58,7 @@ <h3>When Needed</h3>

<p>Information needed to identify controls does not need to be visible all the time. But information needed to identify controls must be visible <i>when the controls are needed</i> without hover interaction or keyboard focus. Controls can be available through a persistent <b><i>visible entry point</i></b>, such as a menu button that opens subitems. In a multi-step process or multi-part form, controls may be hidden in an earlier step or part; however, at the time the user can move the process forward, the information needed to identify the control, which is usually the control itself, must be visible without hover interaction or keyboard focus.</p>

<p>In some cases, controls are provided in multiple locations on a page or at multiple points within a process. In these cases, at least one of the instances of the control must be visible without hover interaction or keyboard focus. For example, in an email process, some controls such as trash may be visible using pointer hover in the inbox list view, but are always visible on the view of the email itself. Because the controls are persistently visible on the email view, they do not need to be persistently visible on the inbox view.</p>
<p>In some cases, controls are provided in multiple locations on a page or at multiple points within a process. In these cases, at least one of the instances of the control must be visible without hover interaction or keyboard focus. For example, on an email listing page some controls such as trash may be visible using pointer hover in the inbox list view. However, those controls are always visible on the email page. Because the controls are persistently visible on the email view, they do not need to be persistently visible on the inbox view.</p>

<h3>Embedded Controls</h3>

Expand All @@ -82,10 +82,9 @@ <h2>Benefits of Visible Controls</h2>
<h2>Examples of Visible Controls</h2>

<ul>
<li>Users with cognitive and learning disabilities can more easily locate controls that allow them to successfully progress through a process.</li> <li>Users with cognitive and learning disabilities, mobility and motor impairments, and low vision can more easily locate controls that allow them to successfully progress through a process.</li>
<li>Users with memory impairments do not need to remember where controls are located</li> <li>Users with memory impairments do not need to remember where controls are located.</li>
<li>Users with low vision do not need to combine visually searching for controls with moving pointer hover or keyboard focus.</li>
<li>Users with mobility and motor impairments who use speech input do not need to use hover or focus to locate and operate controls.</li>
<li>In a web editor, once a page is open for editing, all the possible locations for editing display a pencil icon.</li>
<li>In a web editor, a settings can be changed so that the icons are all shown by default. If the setting isn’t enabled, the possible locations for editing are hidden until a user hovers over them.</li>
<li>When viewing a list of emails the controls needed to delete or forward the email are not visible unless by hovered. When an email has been selected the same controls are persistently visible.</li>
alastc marked this conversation as resolved.
Show resolved Hide resolved
</ul>

</section>
Expand Down