W3C home > Mailing lists > Public > wai-xtech@w3.org > October 2009

Re: WWW/WAI/PF/src aria-implementation.html,1.34,1.35 aria-primer.html,1.4,1.5 aria-roadmap.html,1.4,1.5

From: Simon Pieters <simonp@opera.com>
Date: Thu, 15 Oct 2009 10:20:28 +0200
To: public-pfwg-cvs@w3.org
Cc: "wai-xtech@w3.org" <wai-xtech@w3.org>
Message-ID: <op.u1t1geg4idj3kv@simon-pieterss-macbook.local>
On Wed, 14 Oct 2009 22:09:30 +0200, Michael Cooper via cvs-syncmail  
<cvsmail@w3.org> wrote:

> Update of /w3ccvs/WWW/WAI/PF/src
> In directory hutz:/tmp/cvs-serv19801
>
> Modified Files:
> 	aria-implementation.html aria-primer.html aria-roadmap.html
> Log Message:
> Comment 80

> @@ -146,7 +147,7 @@
>  		<ol>
>  			<li>Where <code>tabindex</code> equals a negative integer, the user  
> agent <span class="rfc2119">must</span> allow the element to be focused,  
> but <span class="rfc2119">must</span> not include the element in the  
> sequential tab order.</li>
>              <li>Where <code>tabindex=&quot;0&quot;</code>, the user  
> agent <span class="rfc2119">must</span> allow the element to be focused  
> and <span class="rfc2119">must</span> include the element in the  
> sequential tab order.</li>
> -            <li>Where <code>tabindex</code> is greater than zero, the  
> user agent <span class="rfc2119">must</span> allow the element to be  
> focused, and <span class="rfc2119">must</span> include the element in  
> the sequential tab order according to the value of the  
> <code>tabindex</code> attribute and before any elements with  
> <code>tabindex</code> either omitted or with a value of zero. See <a  
> HREF="http://www.w3.org/TR/2009/WD-html5-20090212/editing.html#sequential-focus-navigation">Sequential  
> focus navigation</a> for details. </li>
> +            <li>Where <code>tabindex</code> is greater than zero, the  
> user agent <span class="rfc2119">must</span> allow the element to be  
> focused, and <span class="rfc2119">must</span> include the element in  
> the sequential tab order according to the value of the  
> <code>tabindex</code> attribute and before any elements with  
> <code>tabindex</code> either omitted or with a value of zero. See <a  
> href="http://www.w3.org/TR/2009/WD-html5-20090212/editing.html#sequential-focus-navigation">Sequential  
> focus navigation</a> for details. </li>
>              <li>Every HTMLElement <span class="rfc2119">must</span>  
> expose the <code class="dom-property">element.tabIndex</code>  
> property.</li>
>  			<li>The <code class="dom-method">focus</code> and <code  
> class="dom-method">blur</code> methods <span class="rfc2119">must</span>  
> be added to the HTMLElement interface (available to script for every  
> type of element).</li>
>  			<li>Any element that can receive focus <span  
> class="rfc2119">must</span> fire <code class="dom-event">focus</code>  
> and <code class="dom-event">blur</code> events.</li>
> @@ -171,7 +172,7 @@

Shouldn't this part be replaced by a reference to HTML5? HTML5 already  
requires the above things, but might be subtly different (meaning that it  
would be impossible to conform to both specs).

I'd rather there weren't requirements specifying the same thing in two  
different specs.

-- 
Simon Pieters
Opera Software
Received on Thursday, 15 October 2009 08:21:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 13:16:07 GMT