Merge branch 'master' into Support_personalization_only-AAA

Myndex · Aug 15, 2017 · a4573cf · a4573cf
2 parents 95c83c7 + ba7ab43
commit a4573cf
Show file tree

Hide file tree

Showing 39 changed files with 815 additions and 356 deletions.
diff --git a/guidelines/guidelines.css b/guidelines/guidelines.css
@@ -57,4 +57,5 @@ dd.new, dd.proposed {
 	font-size: x-small;
 	display: block;
 	max-width: 25%;
+	hyphens: none;
 }
diff --git a/guidelines/index.html b/guidelines/index.html
diff --git a/guidelines/sc/21/accessible-authentication.html b/guidelines/sc/21/accessible-authentication.html
@@ -1,8 +1,18 @@
-<!--
-<section class="sc proposed">
-   <h4>{handle}</h4>
-   <p class="conformance-level"></p>
-   <p class="change">Proposed</p>
-   <p>{SC text}</p>   					
+
+<section class="sc new">
+   <h4>Accessible Authentication</h4>
+   <p class="conformance-level">A</p>
+   <p class="change">New</p>
+	<p class="ednote">Discussion of the issue is available in <a href="https://github.com/w3c/wcag21/issues/23">Issue 23</a>. To file comments on this proposal, please <a href="https://github.com/w3c/wcag21/issues/new">raise new issues</a> for each discrete comment in GitHub.
+	</p>
+	<p>Essential steps of an authentication process, which rely upon recalling or transcribing information, have one of the following:</p>
+  <ul><li>alternative essential steps, which do not rely upon recalling and transcribing information; or</li><li>
+	an authentication-credentials reset process, which does not rely upon recalling and transcribing information</li></ul>
+  <p>Exceptions:</p>
+  <ul>
+  <li>Authentication process involves basic identifying information to which the user has easy access, such as name, address, email address and identification or social security number.
+  </li>
+  <li>This is not achievable due to legal requirements.   
+  </li>
+  </ul>
 </section>
--->
diff --git a/guidelines/sc/21/accessible-name.html b/guidelines/sc/21/accessible-name.html
@@ -0,0 +1,10 @@
+<section class="sc new">
+   <h4>Accessible Name</h4>
+   <p class="conformance-level">A</p>
+   <p class="change">New</p>
+  <p>Where an active control has a visible label, the <a>accessible name</a> for the control includes the text string used for its visible label.</p>
+  <p class="note">A best practice is to place the text string at the start of the text string.</p>
+	<p class="ednote">Discussion of the issue is available in <a href="https://github.com/w3c/wcag21/issues/68">Issue 68</a>. To file comments on this proposal, please <a href="https://github.com/w3c/wcag21/issues/new">raise new issues</a> for each discrete comment in GitHub.
+	</p>
+
+</section>
diff --git a/guidelines/sc/21/adapting-text.html b/guidelines/sc/21/adapting-text.html
@@ -1,27 +1,22 @@
-<section class="sc proposed">
+<section class="sc new">
 
    <h4>Adapting Text</h4>
 
    <p class="conformance-level">AA</p>
 
-   <p class="change">Proposed</p>
-
-   <p class="issue">This is a proposed Success Criterion that has not yet been formally approved by the
-      Working Group. Discussion of the issue is available in Issues <a href="https://github.com/w3c/wcag21/issues/79">79</a>, <a href="https://github.com/w3c/wcag21/issues/78">78</a>, and <a href="https://github.com/w3c/wcag21/issues/74">74</a> and in <a href="https://github.com/w3c/wcag21/pull/124">Pull request 124</a>. To file comments on this proposal, please <a href="https://github.com/w3c/wcag21/issues/new">raise new issues</a> for each discrete comment in GitHub.
-   </p>
-
-   <p>No loss of content or functionality on a webpage is caused by overriding:</p>
-
+   <p class="change">New</p>
+
+   <p>If the technologies being used allow the <a>user agent</a> to <a>adapt</a> <a>style properties</a> of <a>text</a>, then no loss of <a>essential</a> content or functionality occurs by adapting all of the following:</p>
+
    <ol>
-
-      <li>font family to Verdana, or</li>
-
-      <li>foreground and background to white on black, or</li>
-
-      <li>line height of all text to 1.5, letter spacing to 0.12 em, and word spacing to 0.16
-         em.
-      </li>
-
+     <li>line height (line spacing) to at least 1.5 times the font size</li>
+     <li>spacing underneath paragraphs to at least 2 times the font size</li>
+     <li>letter spacing (tracking) to at least 0.12 times the font size</li>
+     <li>word spacing to at least 0.16 times the font size</li>
    </ol>
+
+   <p class="note">Examples of text that are typically not affected by <a>style properties</a> are open <a>captions</a> and <a>images of text</a>, which are not expected to adapt.</p>
+
+   <p class="ednote">The Working Group seeks to include overriding text color, background color, and font-family as part of this SC, but is not yet able to identify a way to do so that is sufficiently testable.</p>
 
-</section>
+</section>
diff --git a/guidelines/sc/21/change-of-content.html b/guidelines/sc/21/change-of-content.html
@@ -1,33 +1,28 @@
-<section class="sc proposed">
+<section class="sc new">
 
    <h4>Change of Content</h4>
 
    <p class="conformance-level">AA</p>
 
-   <p class="change">Proposed</p>
+   <p class="change">New</p>
 
-   <p class="issue">This is a proposed Success Criterion that has not yet been formally approved by the
-      Working Group. Discussion of the issue is available in <a href="https://github.com/w3c/wcag21/issues/2">Issue 2</a> and <a href="https://github.com/w3c/wcag21/pull/112">Pull Request 112</a>. To file comments on this proposal, please <a href="https://github.com/w3c/wcag21/issues/new">raise new issues</a> for each discrete comment in GitHub.
-   </p>
-
-   <p>Programmatic notification is provided for each <a>change of content</a> that indicates an action was taken or that conveys information, unless one or more
+   <p>Programmatic notification is provided for each <a>change of content</a> that indicates a user action was taken or that conveys information, unless one or more
       of the following is true: 
    </p>
 
-   <ul>
-
-      <li>There is an accessibility supported relationship between the new content and the control
-         that triggers it.
-      </li>
-
-      <li>The user has been advised of the behavior before using the component.</li>
-
-      <li>There are more than 5 notifications per minute.</li>
-
-      <li>The change of content is not a result of a user action AND not related to the the
-         primary purpose of the page.
-      </li>
-
+   <ul>      						
+      <li>There is a programmatically determined relationship between the new content and the control
+         that triggers it;
+      </li>						
+      <li>The user has been advised of the change of content before or as a result of using the control;</li>
+      <li>The change of content is not a result of a user action AND not related to the <a>primary purpose of the page</a>.
+      </li>      					
    </ul>
 
-</section>
+     <p class="note">The Working Group is including this proposed Success Criteria for comment, but has not reached consensus on how to best handle web pages and applications with continual changes of content such as games and simulations and seeks additional input from reviewers on this point.
+   </p>
+
+     <p class="note">Discussion of the issue is available in <a href="https://github.com/w3c/wcag21/issues/2">Issue 2</a>. To file comments on this proposal, please <a href="https://github.com/w3c/wcag21/issues/new">raise new issues</a> for each discrete comment in GitHub.
+   </p>
+
+</section>
diff --git a/guidelines/sc/21/character-key-shortcuts.html b/guidelines/sc/21/character-key-shortcuts.html
@@ -0,0 +1,13 @@
+<section class="sc new">
+
+   <h4>Character Key Shortcuts</h4>
+
+   <p class="conformance-level">A</p>
+
+   <p class="change">New</p>
+
+   <p>If a <a>keyboard shortcut</a> consisting entirely of one or more <a>character keys</a> is implemented by the content, then a mechanism is available to turn it off or to remap it to a shortcut that uses at least one non-character key. </p>
+
+     <p class="note">Discussion of the issue is available in <a href="https://github.com/w3c/wcag21/issues/69">Issue 69</a> and <a href="https://github.com/w3c/wcag21/pull/133">Pull Request 133</a>. To file comments on this proposal, please <a href="https://github.com/w3c/wcag21/issues/new">raise new issues</a> for each discrete comment in GitHub.</p>
+
+</section>
diff --git a/guidelines/sc/21/content-on-hover-or-focus.html b/guidelines/sc/21/content-on-hover-or-focus.html
@@ -0,0 +1,30 @@
+    <section class="sc new">
+
+   <h4>Content on Hover or Focus</h4>
+
+   <p class="conformance-level">AA</p>
+
+   <p class="change">New</p>
+
+   <p class="ednote">Discussion of the issue is available in <a href="https://github.com/w3c/wcag21/issues/75">Issue 75</a>. To file comments on this proposal, please <a href="https://github.com/w3c/wcag21/issues/new">raise new issues</a> for each discrete comment in GitHub.
+   </p>
+
+      <p>When content becomes visible when triggered by a <a>user interface component</a> receiving keyboard focus or pointer hover, the following are true, except where the visual presentation of the content is controlled by the user agent and is not modified by the author:</p>
+
+  <dl>
+
+    <dt>Visible trigger</dt>
+    <dd>Either the additional content does not obscure any <a>essential</a> content within the triggering <a>user interface component</a>, or the additional content can be closed or repositioned by the user.</dd>
+
+    <dt>Hover</dt>
+   <dd>If the additional content is triggered via pointer hover, then that content remains visible when the pointer is moved over it.</dd>
+
+    <dt>Focus</dt>
+    <dd>The additional content remains visible while the triggering user interface component has keyboard focus, unless the user dismisses the additional content.</dd>
+
+  </dl>
+
+      <p class="note">Examples of additional content controlled by the user agent include browser tooltips created through use of the HTML title attribute.</p>
+     <p class="note">Custom tooltips, sub-menus, and other nonmodal popups which display on hover and focus are examples of additional content covered by this criterion.</p>
+
+  </section>
diff --git a/guidelines/sc/21/orientation.html b/guidelines/sc/21/orientation.html
@@ -1,17 +1,16 @@
-<section class="sc proposed">
+<section class="sc new">
 
    <h4>Orientation</h4>
 
    <p class="conformance-level">AA</p>
 
-   <p class="change">Proposed</p>
+   <p class="change">New</p>
 
-   <p class="issue">This is a proposed Success Criterion that has not yet been formally approved by the
-      Working Group. Discussion of the issue is available in <a href="https://github.com/w3c/wcag21/issues/70">Issue 70</a> and <a href="https://github.com/w3c/wcag21/pull/140">Pull Request 140</a>. To file comments on this proposal, please <a href="https://github.com/w3c/wcag21/issues/new">raise new issues</a> for each discrete comment in GitHub.
+   <p class="ednote">Discussion of the issue is available in <a href="https://github.com/w3c/wcag21/issues/70">Issue 70</a>. To file comments on this proposal, please <a href="https://github.com/w3c/wcag21/issues/new">raise new issues</a> for each discrete comment in GitHub.
    </p>
 
-   <p>Content is not locked to a specific <a>orientation</a>, and functionality of the content is operable in all orientations, except where orientation
-      is essential for use of the content.
+   <p>Content is not locked to a specific <a>display orientation</a>, and functionality of the content is operable in all display orientations, except where display orientation
+      is <a>essential</a> for use of the content.
    </p>
 
-</section>
+</section>
diff --git a/guidelines/sc/21/popup-interference-.html b/guidelines/sc/21/popup-interference-.html
diff --git a/guidelines/sc/21/resize-content.html b/guidelines/sc/21/resize-content.html
@@ -1,17 +1,23 @@
 <section class="sc new">
 
-   <h4>Resize content</h4>
+   <h4>Zoom content</h4>
 
-   <p class="conformance-level">A</p>
+   <p class="conformance-level">AA</p>
 
    <p class="change">New</p>
 
-   <p class="issue">Discussion of the issue is available in <a href="https://github.com/w3c/wcag21/issues/77">Issue 77</a> and <a href="https://github.com/w3c/wcag21/pull/120">Pull Request 120</a>. To file comments on this proposal, please <a href="https://github.com/w3c/wcag21/issues/new">raise new issues</a> for each discrete comment in GitHub.
+   <p class="ednote">Discussion of the issue is available in <a href="https://github.com/w3c/wcag21/issues/77">Issue 77</a>. To file comments on this proposal, please <a href="https://github.com/w3c/wcag21/issues/new">raise new issues</a> for each discrete comment in GitHub.
    </p>
 
-   <p>Content can be resized to 400% without loss of content or functionality, and without
-      requiring two-dimensional scrolling except for parts of the content where fixed spatial
-      layout is necessary to use or meaning.
-   </p>
+   <p>Content can be zoomed to an equivalent width of 320 CSS pixels without loss of content or functionality, 
+     and without requiring scrolling on more than one axis except for parts of the content which require 
+     two-dimensional layout for usage or meaning.</p>
+
+   <p class="note">320 CSS pixels is equivalent to a starting viewport width of 1280 CSS pixels wide at 400% zoom. 
+     For web pages which are designed to scroll horizontally, the 320px should be taken as the height rather than width.</p>
+
+   <p class="note">Examples of content which require two-dimensional layout are images, maps, diagrams, 
+     video, games, presentations, data tables, and interfaces where it is necessary to keep toolbars in view while
+     manipulating content.</p>
 
-</section>
+</section>
diff --git a/guidelines/sc/21/single-key-shortcuts.html b/guidelines/sc/21/single-key-shortcuts.html
diff --git a/guidelines/sc/21/target-size-all.html b/guidelines/sc/21/target-size-all.html
@@ -0,0 +1,11 @@
+<section class="sc new">
+
+   <h4>Target Size (no exception)</h4>
+
+   <p class="conformance-level">AAA</p>
+
+   <p class="change">New</p>
+
+  <p>The size of the <a>target</a> is at least 44 by 44 <a>CSS pixels</a> for pointer inputs.</p>
+
+</section>
diff --git a/guidelines/sc/21/target-size.html b/guidelines/sc/21/target-size.html
@@ -1,43 +1,29 @@
-<section class="sc proposed">
+<section class="sc new">
 
    <h4>Target Size</h4>
 
-   <p class="conformance-level">A</p>
-
-   <p class="change">Proposed</p>
-
-   <p class="issue">This is a proposed Success Criterion that has not yet been formally approved by the
-      Working Group. Discussion of the issue is available in <a href="https://github.com/w3c/wcag21/issues/60">Issue 60</a>. To file comments on this proposal, please <a href="https://github.com/w3c/wcag21/issues/new">raise new issues</a> for each discrete comment in GitHub.
-   </p>
-
-   <p>The size of the target in relation to the visible display at the default viewport
-      size is at least:
-   </p>
-
-   <ul>
-
-      <li>44 px by 44 px for pointer inputs with coarse pointing accuracy (such as a touchscreen)</li>
-
-      <li>22 px by 22 px for pointer inputs with fine pointing accuracy (such as a mouse, trackpad
-         or stylus)
-      </li>
-
-   </ul>
-
-   <p>where px is a CSS pixel when the page is using the device ideal viewport.</p>
-
-   <p>Except when a link or control:</p>
-
-   <ul>
-
-      <li>is not part of the primary purpose or function of the page OR</li>
-
-      <li>has an alternative link/control whose target does meet the minimum size requirements</li>
-
-   </ul>
-
-   <p class="note">Editor's Note: this criterion borrows the distinction of "coarse" and "fine" pointing
-      devices from <a href="https://www.w3.org/TR/mediaqueries-4/#pointer">Media Queries Level 4 - Pointing Device Quality: the pointer feature</a> [[!mediaqueries-4]].
-   </p>
-
-</section>
+   <p class="conformance-level">AA</p>
+
+   <p class="change">New</p>
+
+  <p>The size of the <a>target</a> is at least 44 by 44 <a>CSS pixels</a> for <a>pointer inputs</a> except when:</p>
+<dl>
+	<dt>Customizable</dt>
+  <dd>A mechanism is available to change the size of the target independent of the level of page magnification.</dd>
+	<dt>Equivalent</dt> 
+  <dd>The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels.</dd>
+	<dt>Essential</dt> 
+  <dd>A particular presentation of target is <a>essential</a> to the information being conveyed.</dd>
+	<dt>In-Page</dt> 
+  <dd>The target is a text link where the destination is on the same page.</dd>
+	<dt>Inline</dt> 
+  <dd>The target is in a block of text.</dd>
+	<dt>Grouped</dt> 
+  <dd>Targets in groups of more than five have at least one dimension that is 44 pixels and the other is at least 22 pixels.</dd>
+	<dt>User agent control</dt> 
+  <dd>The appearance of the target is determined by the user agent and is not modified by the author.</dd>
+</dl>  
+
+<p class="ednote">The exact parameters of the exception on grouped links are still under discussion by the Working Group.</p>
+
+</section>