Re: ARIA roles added to the a element should be conforming in HTML5.

Tab Atkins Jr. On 09-11-10 17.42:

> On Tue, Nov 10, 2009 at 8:40 AM, Charles McCathieNevile
> <chaals@opera.com> wrote:
>>>>> On Thu, Oct 22, 2009 at 9:08 AM, Leif Halvard Silli wrote:
>>>>>> In the spirit of "don't break the Web", the most important question
>>>>>> seems to me be to be "should it work?" Should a <h1> with a
>>>>>> role="button" be presented as a button in accessibility devices?
>> [a few people with known expertise and experiences in accessibility said
>> Yes. I agree with them.]
> 
> Ok.


So, as a result, an H1 element without any interactivity could be 
presented as if it is interactive. That's the downside.

[...]

>> I have been told various times that HTML 5 is about what happens in the real
>> world (indeed, I promote that benefit consistently in my mnay talks on the
>> topic), but I am ready to see the evidence.
> 
> So you're reasonably certain that presenting that <h1> as a button in
> accessibility devices is indeed a good thing for users?  And that
> officially blessing this usage is better than attempting to evangelize
> for more appropriate usage in the first place, obviating the need for
> ARIA?
> 
> (I'm very interested in the answer to this, because I'm assuming that
> one *can* use appropriate elements in the first place - my own
> experience building websites seems to suggest so.  If in practice
> there are indeed important reasons to subvert HTML's default
> semantics, that's information to know about!)

If we want to avoid that H1 elements can be turned into buttons, 
perhaps we should start by making the following non-conforming?

<a href="link"><h1>Heading</h1></a>
-- 
leif halvard silli

Received on Tuesday, 10 November 2009 18:17:51 UTC