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

Jump to bottom

Initial re-write of SC text #2019

Merged
merged 10 commits into from Dec 17, 2021
Merged

Initial re-write of SC text #2019

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
625604f
Initial re-write of SC text
alastc Aug 26, 2021
9e8a831
tweaking
alastc Aug 26, 2021
7443902
Aligning understanding
alastc Aug 26, 2021
9d9b61e
Adjusting keyboard only exception
alastc Sep 16, 2021
3a04ef5
Updated understanding on keyboard
alastc Sep 16, 2021
391e8f2
typo
alastc Sep 16, 2021
ff1a989
Simpler last bullet
alastc Nov 12, 2021
db42fc1
typo
alastc Dec 3, 2021
6b67d91
typo
alastc Dec 3, 2021
50af1a4
Merge branch 'main' into Issue1840-Visible-controls
alastc Dec 3, 2021
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
10 changes: 5 additions & 5 deletions guidelines/sc/22/visible-controls.html
View file
Open in desktop
Expand Up @@ -5,12 +5,12 @@ <h4>Visible Controls</h4>
<p class="conformance-level">AA</p>
<p class="change">New</p>

<p>Where receiving pointer hover or keyboard focus triggers <a>user interface components</a> to be visible, information needed to identify that user interface components are available is visible, except when:</p>
<p>When <a>user interface components</a> are invisible until hover or focus makes them visible, provide a visible indicator that the components are available, except when:</p>
<ul>
<li>The information needed to identify the user interface components is available through an equivalent component that is visible on the same page or on a different step in a multi-step process without requiring pointer hover or keyboard focus;</li>
<li>The component is provided specifically to enhance the experience for keyboard navigation;</li>
<li>A mechanism is available to make the information persistently visible;</li>
<li>Hiding the information needed to identify the component is <a>essential</a>.</li>
<li>The same functionality is available through a component on the same page, or on a different step in a multi-step process, without requiring pointer hover or keyboard focus to make it visible;</li>
<li>The component provides keyboard-only functionality;</li>
<li>A mechanism is available to make the components persistently visible;</li>
<li>Hiding the visual indicator is <a>essential</a>.</li>
</ul>
<p class="note">User interface components can be available through other visible components such as sub-menus, edit buttons, tabs, or thumbnails of media.</p>
<p class="ednote">The working group is interested in feedback about whether there are Components determined by the user agent that should not be in scope.</p>
Expand Down
12 changes: 7 additions & 5 deletions understanding/22/visible-controls.html
View file
Open in desktop
Expand Up @@ -21,12 +21,12 @@ <h2>Visible Controls Success Criteria Text</h2>
<p class="conformance-level">AA</p>
<p class="change">New</p>

<p>Where receiving pointer hover or keyboard focus triggers <a>user interface components</a> to be visible, information needed to identify that user interface components are available is visible, except when:</p>
<p>When <a>user interface components</a> are invisible until hover or focus makes them visible, provide a visible indicator that the components are available, except when:</p>
<ul>
<li>The information needed to identify the user interface components is available through an equivalent component that is visible on the same page or on a different step in a multi-step process without requiring pointer hover or keyboard focus;</li>
<li>The component is provided specifically to enhance the experience for keyboard navigation;</li>
<li>A mechanism is available to make the information persistently visible;</li>
<li>Hiding the information needed to identify the component is <a>essential</a>.</li>
<li>The same functionality is available through a component on the same page, or on a different step in a multi-step process, without requiring pointer hover or keyboard focus to make it visible;</li>
<li>The component provides keyboard-only functionality;</li>
<li>A mechanism is available to make the components persistently visible;</li>
<li>Hiding the indicator needed to identify the component is available is essential.</li>
</ul>
<p class="note">User interface components can be available through other visible components such as sub-menus, edit buttons, tabs, or thumbnails of media.</p>
<p class="ednote">The working group is interested in feedback about whether there are Components determined by the user agent that should not be in scope.</p>
Expand Down Expand Up @@ -64,6 +64,8 @@ <h3>When Needed</h3>
<li>If hiding the information needed to identify the component is essential. For example, a memory game hides the controls for selecting a card to flip over.</li>
</ul>

<p>The exception for components that provide "keyboard-only functionality" is to allow for features such as skip links, which are not visible by default. As they appear on focus, and are aimed at keyboard-only users, they are not intended to be covered by this criterion.</p>

<h3>Embedded Controls</h3>

<p>Information needed to identify user interface components is usually the component itself; however, there are situations where controls are not visible. Complex components such as video players and carousels often include controls that are visible on hover. The presence of the complex component — for example, the carousel component or the video image — provides the “Information needed to identify the user interface components.” For a carousel, controls displayed on hover should also be displayed when the carousel is activated. For a video player, activating the video image should launch the video (sometimes in a new window), at which point more video player controls, including controls displayed previously on hover, should be visible. Some users may still struggle if video controls are not persistently visible, so there is benefit to providing a mechanism that allows users to have the controls persistently visible.</p>
Expand Down