W3C home > Mailing lists > Public > public-html@w3.org > June 2010

Re: Change proposal for ISSUE-85

From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Wed, 16 Jun 2010 14:59:44 +0200
To: Jonas Sicking <jonas@sicking.cc>
Cc: Maciej Stachowiak <mjs@apple.com>, Ian Hickson <ian@hixie.ch>, Sam Ruby <rubys@intertwingly.net>, Steven Faulkner <faulkner.steve@gmail.com>, public-html@w3.org
Message-ID: <20100616145944268588.faa8d2b8@xn--mlform-iua.no>
Jonas Sicking, Tue, 15 Jun 2010 23:18:51 -0700:
> On Tue, Jun 15, 2010 at 11:10 PM, Maciej Stachowiak wrote:
>> On Jun 15, 2010, at 10:46 PM, Jonas Sicking wrote:
  []
>> HTML5 does not have any requirements that would override or 
>> contradict the WAI-ARIA requirements quoted above.
>> 
>> Thus, UAs are required to respect the role on <a role=button>, 
>> regardless of whether it is conforming or not.
>> 
>>> I think a good argument could be made that if someone has gone through
>>> the trouble to add 'role=button' to an element, then that is likely
>>> the most accurate role. Thus I think a reasonable argument could be
>>> made that we should forward this information to AT users.
>> 
>> I think you are right, and I believe this is already required by the 
>> combination of the relevant specifications.
> 
> Ah, excellent. It might be worth pointing this out in the change
> proposal, though maybe this was obvious to everyone that knows ARIA
> well enough.

+1 For bringing this into Steve's change proposal.

This should be _pointed out_ in HTML5, regardless what is considered 
valid. To not point it out would be inconsistent with the commonly 
cited ideal that developers should not need to look in more than one 
specification.
-- 
leif halvard silli
Received on Wednesday, 16 June 2010 13:00:23 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:10 GMT