[html5] r7001 - [e] (0) Add some notes explaining why these are SHOULDs and not MUSTs. Fixing ht [...]
whatwg at whatwg.org
whatwg at whatwg.org
Wed Feb 15 16:06:24 PST 2012
Author: ianh
Date: 2012-02-15 16:06:23 -0800 (Wed, 15 Feb 2012)
New Revision: 7001
Modified:
complete.html
index
source
Log:
[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
Modified: complete.html
===================================================================
--- complete.html 2012-02-15 23:23:24 UTC (rev 7000)
+++ complete.html 2012-02-16 00:06:23 UTC (rev 7001)
@@ -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 — Last Updated 15 February 2012</h2>
+ <h2 class="no-num no-toc">Living Standard — 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 @@
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 @@
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 @@
-
<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>
Modified: index
===================================================================
--- index 2012-02-15 23:23:24 UTC (rev 7000)
+++ index 2012-02-16 00:06:23 UTC (rev 7001)
@@ -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 — Last Updated 15 February 2012</h2>
+ <h2 class="no-num no-toc">Living Standard — 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 @@
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 @@
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 @@
-
<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>
Modified: source
===================================================================
--- source 2012-02-15 23:23:24 UTC (rev 7000)
+++ source 2012-02-16 00:06:23 UTC (rev 7001)
@@ -83130,6 +83130,11 @@
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 @@
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 @@
-
<h3>Assigning keyboard shortcuts</h3>
<h4>Introduction</h4>
More information about the Commit-Watchers
mailing list