- From: <bugzilla@jessica.w3.org>
- Date: Thu, 09 Sep 2010 11:21:26 +0000
- To: public-html-a11y@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10481 --- Comment #18 from Joshue O Connor <joshue.oconnor@cfit.ie> 2010-09-09 11:21:25 --- (In reply to comment #17) > (In reply to comment #13) > > What differences will there be in an AT user's experience when encountering > > <img role=note> as opposed to when encountering a <img role=img>? > > Testing in VoiceOver on Mac OS X 10.5: > > A role="note" element is expected to have text or element children. Thus if you have <p role="note">Foo</p>, then VoiceOVer reads "Foo". Note that if you had <p role="teapot">Foo</p>, the UA would probably read out "Foo", unless the role is recognised by the UA it will just read out the contents of the containing element. > Wheras for an <img role="note" alt="Foo">, then there are no text or element > children, and thus VoiceOver just stops reading. Ok, that is to be expected. > Whereas if you have <img alt="Foo."> or <img role="img" alt="Foo.">, then >"Foo" is read. That is also to be expected, in HTML4, img==img. The point is that this default is no longer defined the same way in HTML 5. It makes sense to me that the role is defined in a similar way, for backwards compatibility etc and that the element has the capability to take explicit annotations at the authors discretion. The implementation can be modified by UA/AT vendor. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Thursday, 9 September 2010 11:21:27 UTC