- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Mon, 09 Nov 2009 23:21:25 +0100
- To: HTMLWG WG <public-html@w3.org>
Smylers On 09-11-09 22.27: > Leif Halvard Silli writes: > >> Smylers On 09-11-09 21.11: >> >>> Lars Gunther writes: >>> >>>> <a role="button"> should be forbidden when hard-coded onto the >>>> page for these reasons: >>>> >>>> 2. It is possibly confusing if JavaScript is turned off, since it >>>> will not act as a button in that case. >>> What if it has CSS which makes it look like a button (even without >>> JavaScript)? >> First I thought: Stupid question. How it looks should not matter. > > How it looks matters for this scenario, pointed out by Stefan Schnabel, > where instructions say "press the button". Even if that button is > merely a restyle link, and all it's doing is making a navigation > request, users will be consider it be a button: > > http://lists.w3.org/Archives/Public/public-html/2009Oct/0699.html The example that Stefan brought up was that "the manual says 'press the button', but my UA only reports a link". Which, again, is an example of when using a <button> would not be correct. And hence, again, it is only confusing to talk about what the author /should/ have done. Interesting. We can conclude that the semantics of role="button" are not equal to that of <button>. -- leif halvard silli
Received on Monday, 9 November 2009 22:22:01 UTC