Skip to content

Commit

Permalink
Merge remote-tracking branch 'refs/remotes/origin/master' into unders…
Browse files Browse the repository at this point in the history 
…tanding-cleanup
  • Loading branch information
michael-n-cooper committed May 25, 2018
2 parents 0209167 + 5f5aa5b commit 7a3a3e2
Show file tree
Hide file tree
Showing 8 changed files with 26 additions and 26 deletions.
2 changes: 1 addition & 1 deletion understanding/21/identify-purpose.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@ <h2>Techniques</h2>
<section id="sufficient">
<h3>Sufficient</h3>
<ul>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/ARIA11.html">ARIA11: Using ARIA landmarks to identify regions of a page</a> AND</li>
<li><a href="https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA11" class="aria">ARIA11: Using ARIA landmarks to identify regions of a page</a> AND</li>
<li> Provide semantics that enables for symbols on key content (<a href="https://rawgit.com/w3c/coga/master/techniques/index.html">COGA Techniques</a> 4.2) AND</li>
<li>Using microdata to markup user interface components (future link)</li>
</ul>
Expand Down
2 changes: 1 addition & 1 deletion understanding/21/interruptions-minimum.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ <h2>Intent</h2>
<li>Non-critical messages can easily be turned off and on again </li>
</ol>
<p>Changes in content that are not initiated by the user must be avoided. Secondary content (such as special offers or complementary material) should be easily identified, controlled and turned off.</p>
<p>Other potential distractions are covered by existing WCAG Success Criteria <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/time-limits-pause.html">Pause, Stop, Hide</a>, <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-dis-audio.html">Audio Control</a>, <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/seizure-does-not-violate.html">Three Flashes or Below Threshold</a>, <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-noaudio.html">Low or No Background Audio</a>, <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/time-limits-required-behaviors.html">Timing Adjustable</a>. These success criteria are aimed at specific considerations which can have repercussions on certain user groups, but also have a broader effect of reducing distractions for all users.</p>
<p>Other potential distractions are covered by existing WCAG Success Criteria <a href="pause-stop-hide" class="sc">Pause, Stop, Hide</a>, <a href="audio-control" class="sc">Audio Control</a>, <a href="three-flashes-or-below-threshold" class="sc">Three Flashes or Below Threshold</a>, <a href="low-or-no-background-audio" class="sc">Low or No Background Audio</a>, <a href="timing-adjustable" class="sc">Timing Adjustable</a>. These success criteria are aimed at specific considerations which can have repercussions on certain user groups, but also have a broader effect of reducing distractions for all users.</p>

</section>
<section id="benefits">
Expand Down
8 changes: 4 additions & 4 deletions understanding/21/non-text-contrast.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -376,17 +376,17 @@ <h4>Graphics with sufficient contrast</h4>
<h4>Text in or over graphics</h4>
<ul>
<li>Include labels and values with the graphic (TBD)</li>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/G18.html">G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text</a></li>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/G145.html">G145: Ensuring that a contrast ratio of at least 3:1 exists between text (and images of text) and background behind the text</a></li>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/G174.html">G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast</a></li>
<li><a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G18" class="general">G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text</a></li>
<li><a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G145" class="general">G145: Ensuring that a contrast ratio of at least 3:1 exists between text (and images of text) and background behind the text</a></li>
<li><a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G174" class="general">G174: Providing a control with a sufficient contrast ratio that allows users to switch to a presentation that uses sufficient contrast</a></li>
<li><a href="https://www.w3.org/WAI/GL/wiki/Using_sufficient_contrast_for_images_that_convey_information">Using sufficient contrast for images that convey information (Draft)</a></li>
</ul>
</section>
</section>
<section id="advisory">
<h3>Advisory</h3>
<ul>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/G183.html">G183: Using a contrast ratio of 4.5:1 with surrounding text and providing additional visual cues on focus for links or controls where color alone is used to identify them</a></li>
<li><a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G183" class="general">G183: Using a contrast ratio of 4.5:1 with surrounding text and providing additional visual cues on focus for links or controls where color alone is used to identify them</a></li>
</ul>
</section>
</section>
Expand Down
6 changes: 3 additions & 3 deletions understanding/21/reflow.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ <h3>Avoiding scrolling in horizontally and vertically written languages</h3>
<p>The success Criterion applies to both horizontally and verticaly written languages. Zooming the page for horizontally written languages where pages scroll vertically by default (e.g. English) should not require horizontal scrolling. Zooming the page for vertically written languages which scroll horizontally by default should not require vertical scrolling.</p>

<h3>The relation of Reflow to the Success Criterion 1.4.4 Resize Text</h3>
<p>The focus of the Reflow Success Criterion is to enable users to zoom in without having to scroll in two directions. The Resize Text (<a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-scale.html">Success criterion 1.4.4</a>) also applies, so it should be possible to increase the size of all text by at least 200% <em>as well</em>. If text is reduced in size when people zoom in (or for small-screen usage), it should still be possible to get to 200% bigger. For example, if text is set at 20px when the window is 1280px wide, at 200% zoom it should be at least 20px (so 200% larger), but at 400% zoom it could be set to 10px (therefore still 200% larger than the 100% view. It is not required to be 200% larger at every breakpoint, but it should be possible to get 200% large text in some way.</p>
<p>The focus of the Reflow Success Criterion is to enable users to zoom in without having to scroll in two directions. The Resize Text (<a href="resize-text" class="sc">Success criterion 1.4.4</a>) also applies, so it should be possible to increase the size of all text by at least 200% <em>as well</em>. If text is reduced in size when people zoom in (or for small-screen usage), it should still be possible to get to 200% bigger. For example, if text is set at 20px when the window is 1280px wide, at 200% zoom it should be at least 20px (so 200% larger), but at 400% zoom it could be set to 10px (therefore still 200% larger than the 100% view. It is not required to be 200% larger at every breakpoint, but it should be possible to get 200% large text in some way.</p>
</section>

<section id="benefits">
Expand Down Expand Up @@ -84,8 +84,8 @@ <h3>Sufficient Techniques</h3>
<li> Using media queries (CSS). Ref: <a href="http://blog.cloudfour.com/the-ems-have-it-proportional-media-queries-ftw/"> em based media queries</a> AND</li>
<li>@@ New: Using CSS grids to reflow content (CSS). Ref: <a href="http://alistapart.com/article/fluidgrids"> fluid grids</a> OR</li>
<li>@@ New: Using CSS Flexbox to reflow content (CSS). OR</li>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/SCR34"> SCR34: Calculating size and position in a way that scales with text size (Scripting)</a></li>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/G206"> G206: Providing options within the content to switch to a layout that does not require the user to scroll horizontally to read a line of text</a></li>
<li><a href="https://www.w3.org/WAI/WCAG21/Techniques/client-side-script/SCR34" class="script"> SCR34: Calculating size and position in a way that scales with text size (Scripting)</a></li>
<li><a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G206" class="general"> G206: Providing options within the content to switch to a layout that does not require the user to scroll horizontally to read a line of text</a></li>
<li>@@ New: Using PDF/UA when creating PDFs.</li>
</ul>
</section>
Expand Down
24 changes: 12 additions & 12 deletions understanding/21/status-messages.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,7 @@ <h3 id="excepted-examples">Examples of Changes That Are Not Status Messages</h3>
</li>
<li>
<p>Content is exposed or hidden when a user interacts with a user interface component, for example expanding components such as a menu, select, accordion or tree, or selecting a different tab item in a tablist.</p>
<p>None of the resulting changes to content meet the definition of status messages. Further, all components that meet the definition of a user interface component already have requirements specified under <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-rsv.html#user-interface-componentdef">4.1.2 Name, Role, Value</a>, including the need to make notifications of changes to values and states available to user agents, including assistive technologies. As a result, changes in state, such as "expanded" or "collapsed," would be announced by the screen reader, and thus the user would be alerted to the 'addition' or 'removal' of content. As such, such content does not need to be addressed by this Success Criterion.</p>
<p>None of the resulting changes to content meet the definition of status messages. Further, all components that meet the definition of a user interface component already have requirements specified under <a href="name-role-value" class="sc">4.1.2 Name, Role, Value</a>, including the need to make notifications of changes to values and states available to user agents, including assistive technologies. As a result, changes in state, such as "expanded" or "collapsed," would be announced by the screen reader, and thus the user would be alerted to the 'addition' or 'removal' of content. As such, such content does not need to be addressed by this Success Criterion.</p>

</li>
<li>
Expand Down Expand Up @@ -108,23 +108,23 @@ <h4>Situation A: If a status message advises on the success or results of an act
<ul>
<li><a href="aria-status-role.html">Using <code>role="status"</code></a> @@@ technique created but URL unknown @@@ in combination with any of the following:
<ul>
<li><a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/G199">G199: Providing success feedback when data is submitted successfully</a></li>
<li><a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G199" class="general">G199: Providing success feedback when data is submitted successfully</a></li>
</ul>

</li>
</ul>

<h4>Situation B: If a status message conveys a suggestion, or a warning on the existence of an error:</h4>
<ul>
<li><a href="https://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/ARIA19">ARIA19: Using ARIA role=alert or Live Regions to Identify Errors</a> in combination with any of the following:
<li><a href="https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA19" class="aria">ARIA19: Using ARIA role=alert or Live Regions to Identify Errors</a> in combination with any of the following:
<ul>

<li><a href="https://www.w3.org/TR/WCAG-TECHS/G83.html">G83: Providing text descriptions to identify required fields that were not completed</a></li>
<li><a href="http://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/G84">G84: Providing a text description when the user provides information that is not in the list of allowed values</a></li>
<li><a href="http://www.w3.org/TR/2016/NOTE-WCAG20-TECHS-20161007/G85">G85: Providing a text description when user input falls outside the required format or values</a></li>
<li><a href="https://www.w3.org/TR/WCAG-TECHS/G139.html">G139: Creating a mechanism that allows users to jump to errors</a></li>
<li><a href="https://www.w3.org/TR/WCAG-TECHS/G177.html">G177: Providing suggested correction text</a></li>
<li><a href="https://www.w3.org/TR/WCAG-TECHS/G194.html">G194: Providing spell checking and suggestions for text input</a></li>
<li><a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G83" class="general">G83: Providing text descriptions to identify required fields that were not completed</a></li>
<li><a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G84" class="general">G84: Providing a text description when the user provides information that is not in the list of allowed values</a></li>
<li><a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G85" class="general">G85: Providing a text description when user input falls outside the required format or values</a></li>
<li><a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G139" class="general">G139: Creating a mechanism that allows users to jump to errors</a></li>
<li><a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G177" class="general">G177: Providing suggested correction text</a></li>
<li><a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G194" class="general">G194: Providing spell checking and suggestions for text input</a></li>

</ul>
<p>Note: Not all examples in the preceding general techniques use status messages to convey warnings or errors to users. A role of "alert" is only necessary where a change of context does <em>not</em> take place.</p>
Expand All @@ -136,7 +136,7 @@ <h4>Situation C: If a status message conveys information on the progress of a pr

<li><a href="aria-log-role.html" >Using <code>role="log"</code></a> @@@ technique created but URL unknown</li>
<li>Using <code>role="progressbar"</code> (future link)</li>
<li><a href="aria-status-role.html">Using <code>role="status"</code></a> @@@ URL to update @@@ in combination with <a href="https://www.w3.org/TR/WCAG-TECHS/G193.html">G193: Providing help by an assistant in the Web page</a></li>
<li><a href="aria-status-role.html">Using <code>role="status"</code></a> @@@ URL to update @@@ in combination with <a href="https://www.w3.org/WAI/WCAG21/Techniques/general/G193" class="general">G193: Providing help by an assistant in the Web page</a></li>
</ul>
</section>
</section>
Expand All @@ -147,8 +147,8 @@ <h3>Advisory</h3>
<li>Using aria-live regions to support <a href="https://www.w3.org/WAI/WCAG21/Understanding/content-on-hover-or-focus.html">1.4.13 Content on Hover or Focus</a> (future link)</li>
<li>Using <code>role="marquee"</code> (future link)</li>
<li>Using <code>role="timer"</code> (future link)</li>
<li>Moving focus to new content, including by using <code>alertdialog</code> and <code>dialog</code>; <a href="https://www.w3.org/TR/WCAG-TECHS/ARIA18.html">ARIA18: Using <code>aria-alertdialog</code> to Identify Errors</a></li>
<li>Support personalization by providing an option for users to set a preference on live content; <a href="https://www.w3.org/TR/WCAG-TECHS/SCR14.html">SCR14: Using scripts to make nonessential alerts optional</a></li>
<li>Moving focus to new content, including by using <code>alertdialog</code> and <code>dialog</code>; <a href="https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA18" class="aria">ARIA18: Using <code>aria-alertdialog</code> to Identify Errors</a></li>
<li>Support personalization by providing an option for users to set a preference on live content; <a href="https://www.w3.org/WAI/WCAG21/Techniques/client-side-script/SCR14" class="script">SCR14: Using scripts to make nonessential alerts optional</a></li>
</ul>

</section>
Expand Down
2 changes: 1 addition & 1 deletion understanding/21/target-size-enhanced.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ <h2>Resources</h2>
</section>
<section id="techniques">
<h2>Techniques</h2>
<p>Each numbered item in this section represents a technique or combination of techniques that the <acronym title="Web Content Accessibility Guidelines">WCAG</acronym>Working Group deems sufficient for meeting this Success Criterion. However, it is not necessary to use these particular techniques. For information on using other techniques, see <a href="http://www.w3.org/TR/2016/NOTE-UNDERSTANDING-WCAG20-20161007/understanding-techniques.html">Understanding Techniques for WCAG Success Criteria</a>, particularly the "Other Techniques" section.</p>
<p>Each numbered item in this section represents a technique or combination of techniques that the <acronym title="Web Content Accessibility Guidelines">WCAG</acronym>Working Group deems sufficient for meeting this Success Criterion. However, it is not necessary to use these particular techniques. For information on using other techniques, see <a href="understanding-techniques" class="understanding">Understanding Techniques for WCAG Success Criteria</a>, particularly the "Other Techniques" section.</p>
<section id="sufficient">
<h3>Sufficient</h3>
<p class="instructions">Techniques that are sufficient to meet the Guideline or Success Criterion.</p>
Expand Down
2 changes: 1 addition & 1 deletion understanding/21/target-size.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ <h2>Resources</h2>
<section id="techniques">
<h2>Techniques</h2>
<p>Each numbered item in this section represents a technique or combination of techniques that the <abbr title="Web Content Accessibility Guidelines">WCAG</abbr>Working Group deems sufficient for meeting this Success Criterion. However, it is not
necessary to use these particular techniques. For information on using other techniques, see <a href="http://www.w3.org/TR/2016/NOTE-UNDERSTANDING-WCAG20-20161007/understanding-techniques.html">Understanding Techniques for WCAG Success Criteria</a>,
necessary to use these particular techniques. For information on using other techniques, see <a href="understanding-techniques" class="understanding">Understanding Techniques for WCAG Success Criteria</a>,
particularly the "Other Techniques" section.</p>
<section id="sufficient">
<h3>Sufficient</h3>
Expand Down
6 changes: 3 additions & 3 deletions understanding/21/text-spacing.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -137,9 +137,9 @@ <h3>Sufficient</h3>
<section id="advisory">
<h3>Advisory</h3>
<ul>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/C8.html">C8: Using CSS letter-spacing to control spacing within a word</a></li>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/C21.html">C21: Specifying line spacing in CSS</a></li>
<li><a href="https://www.w3.org/TR/WCAG20-TECHS/C28.html">C28: Specifying the size of text containers using em units </a></li>
<li><a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C8" class="css">C8: Using CSS letter-spacing to control spacing within a word</a></li>
<li><a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C21" class="css">C21: Specifying line spacing in CSS</a></li>
<li><a href="https://www.w3.org/WAI/WCAG21/Techniques/css/C28" class="css">C28: Specifying the size of text containers using em units </a></li>
</ul>
</section>
<section id="failure">
Expand Down

0 comments on commit 7a3a3e2

Please sign in to comment.