- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Fri, 31 Jan 2014 04:48:40 +0100
- To: Cynthia Shelly <cyns@microsoft.com>
- Cc: Bryan Garaventa <bryan.garaventa@whatsock.com>, "T.V Raman" <raman@google.com>, "jongund@illinois.edu" <jongund@illinois.edu>, "jason@jasonjgw.net" <jason@jasonjgw.net>, "wai-xtech@w3.org" <wai-xtech@w3.org>, "w3c-wai-pf@w3.org" <w3c-wai-pf@w3.org>
Cynthia Shelly, Wed, 29 Jan 2014 00:54:14 +0000: > Some of other ideas... > I kind of like role=span. I think it will be really obvious to html > devs what this does. It will be a little goofy to devs moving from > Windows and other native platform APIs to web, but I think the > parallel to HTML will be fairly easy to explain to them. I like the idea, as it is similar to the logic behind role="img". Namely, it is a name that builds on authors’ experience. However, as I just replied to James, I think role="div" would be better. Or may be we should have two roles, with same effect: role=span and role=div. If one has to choose, then I think role=div is better than role=span because I think authors more frequently will be canceling the role of block elements than of inline elements. However, may be I am wrong. Role=span would also be OK. > I'd use something else for decorative images. […] > keep presentation for this use, as it's pretty similar and widely > deployed. +1 -- leif halvard silli
Received on Friday, 31 January 2014 03:49:09 UTC