Add explanation of what "automatic" means in 2.2.2 and 1.4.2, cross-reference #4012
Conversation
… cross-references to related/overlapping SCs.
✅ Deploy Preview for wcag2 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
patrickhlauke
changed the title
|
Noting here though that if the WG feels that "automatically" literally only refers to things happening on a timer, and not as the result of any interaction, then this PR would introduce a breaking change, so would need to be neutered/repointed - which could be done relatively straightforwardly here. In short, the group needs to decide:
(in hindsight, it almost feels like 2.3.3 could have been unnecessary if "starts automatically" had actually been defined properly ... so here we're left trying to disentangle potential overlaps) |
understanding/20/audio-control.html
Outdated
|
|
||
| <p>See also <a href="low-or-no-background-audio">1.4.7 Low or No Background Audio</a>.</p> | ||
| <p>In the context of this Success Criterion, "plays automatically" broadly refers to audio that | ||
| is not stated/played as a direct result of a user's explicit activation.</p> |
There was a problem hiding this comment.
typo: started/played
| <section id="brief"> | ||
| <h2>In brief</h2> | ||
| <dl> | ||
| <dt>Goal</dt><dd>Fewer users are distracted by content that updates or moves.</dd> | ||
| <dt>What to do</dt><dd>Let users control content changes that occur in parallel with other content.</dd> | ||
| <dt>Why it's important</dt><dd>Some people with cognitive disabilities and attention deficits cannot concentrate with continual movement.</dd> | ||
| <dt>Why it's important</dt><dd>Some people with cognitive disabilities and attention deficits cannot concentrate with continual movement.</dd> |
There was a problem hiding this comment.
with continual movement
maybe better "...when distracted by continuous movement"?
or, more verbose: "...when they are distracted by continuous movement" (not sure if "continuous" is better than "continual", at least it seems more common to me)...
| <a href="timing-adjustable">2.2.1: Timing Adjustable</a> for additional requirements related to time-limits for reading. | ||
| </p> | ||
|
|
||
| <p>See <a href="timing-adjustable">2.2.1: Timing Adjustable</a> for additional requirements related to time-limits for reading.</p> |
There was a problem hiding this comment.
for reading
and importantly for providing input via forms - maybe add that?
| auto-updating visual content. For audio content that starts automatically, refer to <a href="audio-control">1.4.2 Audio Control</a>.</p> | ||
| <p>Moving, blinking, scrolling content that starts automatically not as a result of explicit *activation* (such as activating a button), | ||
| but because of a more general user interaction (such as focusing/hovering over an element, or scrolling the page), and doesn't provide | ||
| a way to Pause, Stop, or Hide, will fail this Criterion, and potentially |
There was a problem hiding this comment.
"...and doesn't provide a way tp Pause, Stop, or Hide, will fail..."
This seems a bit clumsy. Maybe more compact and easier to write "...without providing a way to Pause, Stop, or Hide, will fail..."
|
|
||
|
|
||
| <div class="note"> | ||
| <p>"Flashing" content that starts automatically will fail this Success Criterion, as well as <a href="three-flashes">2.3.2 Three Flashes</a> |
There was a problem hiding this comment.
Not sure cross-referencing 2.3.2 / 2.3.1 here is that helpful - it might then need to reiterate the exceptions of 2.2.2 - because if flashes take 4 sec they'd fail 2.3.2 but would pass 2.2.2?
|
Group to review independently before next meeting. MOving to 'ready for review" |
Closes #2863
This is an alternative to #2906 which more directly addresses the definition, as well as providing further explanation/cross-linking for overlapping SCs: