[e] (0) Add some notes explaining why these are SHOULDs and not MUSTs.

Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=13532 Affected topics: HTML git-svn-id: http://svn.whatwg.org/webapps@7001 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Feb 16, 2012 · e0d4e77 · e0d4e77
1 parent 0f63d80
commit e0d4e77
Show file tree

Hide file tree

Showing 3 changed files with 42 additions and 5 deletions.
diff --git a/complete.html b/complete.html
@@ -240,7 +240,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 15 February 2012</h2>
+    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 16 February 2012</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -71126,6 +71126,11 @@ <h4 id=sequential-focus-navigation-and-the-tabindex-attribute><span class=secno>
     be reached using sequential focus navigation, and if so, what its
     relative order should be.</p>
 
+    <p class=note>One valid reason to ignore the platform
+    conventions and always allow an element to be focused would be if
+    the user's only mechanism for activating an element is through a
+    keyboard action that triggers the focused element.</p>
+
    </dd>
 
    <dt id=negative-tabindex>If the value is a negative integer</dt>
@@ -71136,6 +71141,14 @@ <h4 id=sequential-focus-navigation-and-the-tabindex-attribute><span class=secno>
     not allow the element to be reached using sequential focus
     navigation.</p>
 
+    <p class=note>One valid reason to ignore the requirement that
+    sequential focus navigation not allow the author to lead to the
+    element would be if the user's only mechanism for moving the focus
+    is sequential focus navigation. For instance, a keyboard-only user
+    would be unable to click on a text field with a negative <code title=attr-tabindex><a href=#attr-tabindex>tabindex</a></code>, so that user's user agent
+    would be well justified in allowing the user to tab to the control
+    regardless.</p>
+
    </dd>
 
    <dt>If the value is a zero</dt>
@@ -71486,7 +71499,6 @@ <h4 id=element-level-focus-apis><span class=secno>8.3.4 </span>Element-level foc
 
 
 
-
   <h3 id=assigning-keyboard-shortcuts><span class=secno>8.4 </span>Assigning keyboard shortcuts</h3>
 
   <h4 id=introduction-7><span class=secno>8.4.1 </span>Introduction</h4>

diff --git a/index b/index
@@ -240,7 +240,7 @@
 
   <header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
    <hgroup><h1 class=allcaps>HTML</h1>
-    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 15 February 2012</h2>
+    <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 16 February 2012</h2>
    </hgroup><dl><dt><strong>Web developer edition:</strong></dt>
     <dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
     <dt>Multiple-page version:</dt>
@@ -71126,6 +71126,11 @@ interface <dfn id=navigatorstorageutils>NavigatorStorageUtils</dfn> {
     be reached using sequential focus navigation, and if so, what its
     relative order should be.</p>
 
+    <p class=note>One valid reason to ignore the platform
+    conventions and always allow an element to be focused would be if
+    the user's only mechanism for activating an element is through a
+    keyboard action that triggers the focused element.</p>
+
    </dd>
 
    <dt id=negative-tabindex>If the value is a negative integer</dt>
@@ -71136,6 +71141,14 @@ interface <dfn id=navigatorstorageutils>NavigatorStorageUtils</dfn> {
     not allow the element to be reached using sequential focus
     navigation.</p>
 
+    <p class=note>One valid reason to ignore the requirement that
+    sequential focus navigation not allow the author to lead to the
+    element would be if the user's only mechanism for moving the focus
+    is sequential focus navigation. For instance, a keyboard-only user
+    would be unable to click on a text field with a negative <code title=attr-tabindex><a href=#attr-tabindex>tabindex</a></code>, so that user's user agent
+    would be well justified in allowing the user to tab to the control
+    regardless.</p>
+
    </dd>
 
    <dt>If the value is a zero</dt>
@@ -71486,7 +71499,6 @@ interface <dfn id=navigatorstorageutils>NavigatorStorageUtils</dfn> {
 
 
 
-
   <h3 id=assigning-keyboard-shortcuts><span class=secno>8.4 </span>Assigning keyboard shortcuts</h3>
 
   <h4 id=introduction-7><span class=secno>8.4.1 </span>Introduction</h4>

diff --git a/source b/source
@@ -83130,6 +83130,11 @@ interface <dfn>NavigatorStorageUtils</dfn> {
     be reached using sequential focus navigation, and if so, what its
     relative order should be.</p>
 
+    <p class="note">One valid reason to ignore the platform
+    conventions and always allow an element to be focused would be if
+    the user's only mechanism for activating an element is through a
+    keyboard action that triggers the focused element.</p>
+
    </dd>
 
    <dt id="negative-tabindex">If the value is a negative integer</dt>
@@ -83140,6 +83145,15 @@ interface <dfn>NavigatorStorageUtils</dfn> {
     not allow the element to be reached using sequential focus
     navigation.</p>
 
+    <p class="note">One valid reason to ignore the requirement that
+    sequential focus navigation not allow the author to lead to the
+    element would be if the user's only mechanism for moving the focus
+    is sequential focus navigation. For instance, a keyboard-only user
+    would be unable to click on a text field with a negative <code
+    title="attr-tabindex">tabindex</code>, so that user's user agent
+    would be well justified in allowing the user to tab to the control
+    regardless.</p>
+
    </dd>
 
    <dt>If the value is a zero</dt>
@@ -83554,7 +83568,6 @@ interface <dfn>NavigatorStorageUtils</dfn> {
 
 
 
-
   <h3>Assigning keyboard shortcuts</h3>
 
   <h4>Introduction</h4>