- From: Joseph Scheuhammer <clown@alum.mit.edu>
- Date: Mon, 25 Jan 2016 12:12:09 -0500
- To: Richard Schwerdtfeger <schwer@us.ibm.com>
- Cc: jcraig@apple.com, public-aria@w3.org
On 2016-01-25 11:12 AM, Richard Schwerdtfeger wrote:
> 4. As Joseph points out you are not supposed to get at the DOM when it
> is used as an img source. This may be why keyboard access does not work.
Point of clarification: all I have said is that you can't get at the
DOM of the svg referenced from a <img> element. I've not made any
judgment whether you should or not.
I'm leaning towards, "it should work like <iframe src='svg'>" where you
can access the svg DOM through iframe.contentDocument or
iframe.getSVGDocument().
A reason for doing this is that if you include the exact same svg inline
in the html, it renders exactly the same onscreen. The user can't tell
how the image got there. But, in the inline case, the svg DOM is a
subtree of the html DOM.
But, on the other hand, as you note, putting tabindex and keyboard
access for individual svg elements works differently in the two cases.
That might be a reason to continue to treat them differently, DOM-wise;
I'm not sure. I imagine click activation works differently too: as you
say, the svg is inert in the <img> case.
--
;;;;joseph.
'Die Wahrheit ist Irgendwo da Draußsen. Wieder.'
- C. Carter -
Received on Monday, 25 January 2016 17:12:39 UTC