- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Fri, 17 Aug 2012 01:04:20 +0200
- To: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
- Cc: Charles Pritchard <chuck@jumis.com>, David Singer <singer@apple.com>, John Foliot <john@foliot.ca>, Maciej Stachowiak <mjs@apple.com>, Sam Ruby <rubys@intertwingly.net>, "public-html@w3.org" <public-html@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>
Benjamin Hawkes-Lewis, Thu, 16 Aug 2012 23:36:59 +0100: > On Thu, Aug 16, 2012 at 10:18 PM, Charles Pritchard <chuck@jumis.com> wrote: >>>> Hypertext links are a key issue in this discussion >>> >>> Are they? >> >> Yes: while the a11y tree can collapse, expand and mutate (aria-live, >> aria-hidden, etc), such items are part of the current document's workflow. >> @longdesc may link to a new URL: think a href target=iframe. > > Note "hyperlink" is not necessarily a link to another document. But Charles did not say that you couldn't do <a href=#fragment target=iframe>Description</a> The assumption being, I think, that the frame is already in focus - you just fill it with some other content. I have often made the similar point that that @longdesc is like <a href=URL target=_blank>Description</a> And I think that this is a much more realistic assumption. (For instance, because Webkit browsers do not give focus to in-page locations, such as a in-page iframe element.[1]) For a user without visual access, it shouldn't matter whether it opens in a new page or in new frame. [1] https://bugs.webkit.org/show_bug.cgi?id=26856#c0 -- Leif Halvard Silli
Received on Thursday, 16 August 2012 23:05:00 UTC