Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
[e] (0) Apply W3C WG chair decision.
Affected topics: DOM APIs, HTML

git-svn-id: http://svn.whatwg.org/webapps@7058 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
Hixie committed Apr 18, 2012
1 parent 9fda389 commit 13cc9d6
Show file tree
Hide file tree
Showing 3 changed files with 45 additions and 0 deletions.
12 changes: 12 additions & 0 deletions complete.html
Expand Up @@ -1519,6 +1519,12 @@ <h6 class=no-toc id=how-do-the-whatwg-and-w3c-specifications-differ?><span class
<a href=http://lists.w3.org/Archives/Public/public-html/2012Mar/0785.html>third</a>.
</li><!--FORK--><!--TITLE-->

<li>The W3C HTML specification omits some advice about how to
remove focus outlines in an accessible manner (instead only urging
authors not to remove them without giving an alternative to address
the "they're ugly" use case), because of a <a href=http://lists.w3.org/Archives/Public/public-html/2012Mar/0786.html>working
group chair decision from March 2012</a>.</li>

</ul><p>The following sections are only published in the WHATWG
specifications and are not currently available anywhere else:</p>

Expand Down Expand Up @@ -74354,13 +74360,19 @@ <h4 id=element-level-focus-apis><span class=secno>8.4.4 </span>Element-level foc
<p>Unfocuses the element. Use of this method is discouraged. Focus
another element instead.</p>

<!--FORK-->
<p>Do not use this method to hide the focus ring if you find the
focus ring unsightly. Instead, use a CSS rule to override the
'outline' property. (Be aware, however, that this makes the page
significantly less usable for some people, especially those with
reduced vision who use focus outlines to help them navigate the
page.)</p>

<!-- we suggest using CSS here because users can override CSS, so
it's no the end of the world, unlike using .blur(), which cannot
be easily overridden by users and completely breaks tab
navigation. -->

<div class=example>

<p>For example, to hide the outline from links, you could use:</p>
Expand Down
12 changes: 12 additions & 0 deletions index
Expand Up @@ -1519,6 +1519,12 @@
<a href=http://lists.w3.org/Archives/Public/public-html/2012Mar/0785.html>third</a>.
</li><!--FORK--><!--TITLE-->

<li>The W3C HTML specification omits some advice about how to
remove focus outlines in an accessible manner (instead only urging
authors not to remove them without giving an alternative to address
the "they're ugly" use case), because of a <a href=http://lists.w3.org/Archives/Public/public-html/2012Mar/0786.html>working
group chair decision from March 2012</a>.</li>

</ul><p>The following sections are only published in the WHATWG
specifications and are not currently available anywhere else:</p>

Expand Down Expand Up @@ -74354,13 +74360,19 @@ interface <dfn id=navigatorstorageutils>NavigatorStorageUtils</dfn> {
<p>Unfocuses the element. Use of this method is discouraged. Focus
another element instead.</p>

<!--FORK-->
<p>Do not use this method to hide the focus ring if you find the
focus ring unsightly. Instead, use a CSS rule to override the
'outline' property. (Be aware, however, that this makes the page
significantly less usable for some people, especially those with
reduced vision who use focus outlines to help them navigate the
page.)</p>

<!-- we suggest using CSS here because users can override CSS, so
it's no the end of the world, unlike using .blur(), which cannot
be easily overridden by users and completely breaks tab
navigation. -->

<div class=example>

<p>For example, to hide the outline from links, you could use:</p>
Expand Down
21 changes: 21 additions & 0 deletions source
Expand Up @@ -245,6 +245,13 @@
<a href="http://lists.w3.org/Archives/Public/public-html/2012Mar/0785.html">third</a>.
</li><!--FORK--><!--TITLE-->

<li>The W3C HTML specification omits some advice about how to
remove focus outlines in an accessible manner (instead only urging
authors not to remove them without giving an alternative to address
the "they're ugly" use case), because of a <a
href="http://lists.w3.org/Archives/Public/public-html/2012Mar/0786.html">working
group chair decision from March 2012</a>.</li>

</ul>

<p>The following sections are only published in the WHATWG
Expand Down Expand Up @@ -86928,20 +86935,34 @@ interface <dfn>NavigatorStorageUtils</dfn> {
<p>Unfocuses the element. Use of this method is discouraged. Focus
another element instead.</p>

<!--END w3c-html--><!--FORK-->
<p>Do not use this method to hide the focus ring if you find the
focus ring unsightly. Instead, use a CSS rule to override the
'outline' property. (Be aware, however, that this makes the page
significantly less usable for some people, especially those with
reduced vision who use focus outlines to help them navigate the
page.)</p>

<!-- we suggest using CSS here because users can override CSS, so
it's no the end of the world, unlike using .blur(), which cannot
be easily overridden by users and completely breaks tab
navigation. -->

<div class="example">

<p>For example, to hide the outline from links, you could use:</p>

<pre>:link:focus, :visited:focus { outline: none; }</pre>

</div>
<!--START w3c-html--><!--END complete--><!--END dev-html--><!--FORK-->
<p>Do not use this method to hide the focus ring. Do not use any
other method that hides the focus ring from keyboard users,in
particluar do not use a CSS rule to override the 'outline'
property. Removal of the focus ring leads to serious accessibility
issues for users who navigate and interact with interactive
content using the keyboard.</p>
<!--START complete--><!--START dev-html--><!--FORK-->

</dd>

Expand Down

0 comments on commit 13cc9d6

Please sign in to comment.