Re: ACTION-1380 and ACTION-1700

Possible modified text, based on the discussion on the teleconference:

An HTML <img> element is always treated as a single entity, with no child
contents,
regardless of whether the source image is a complex document such as an
SVG (<img src=“foo.svg”>).
An <img> element with role="presentation" or role="none"
therefore is effectively hidden from the accessibility tree.
If the author intends for the content of the image document to be
accessible to users,
it should be embedded using an <object> , <embed>, or <iframe>,
or (for SVG images) included inline in the main document.

On 26 January 2016 at 11:05, Richard Schwerdtfeger <richschwer@gmail.com>
wrote:

> Thanks for the revisions. I did not mean that the browser should expose
> the DOM for the embedded graphics document per the loss of keyboard
> navigation. I am referring to the embedding of the actual SVG document by
> the author.
>
> Revised text:
>
> When the <img> is used to refer to either a raster image (e.g. <img
> src=“foo.jpg”>) or a vector graphics image <img src=“foo.svg”> it is
> treated as a single entity with all descendant elements being
> presentational. This is regardless of whether the target graphic has
> descendant elements that would normally be exposed to assistive
> technologies, such as with an SVG document. Consequently, using a
> role=“presentation” or role=“none” on an <img> element is equivalent to
> using aria-hidden=“true”. If it is possible to make the descendant elements
> accessible the author SHOULD embed the document directly within the host
> document without it being referred to by <img>.
>
>
> be inserted before the text found in role="presentation":
>
> "For any element with an explicit or inherited role of presentation, user
> agents *MUST* ignore any non-global, role-specific WAI-ARIA states and
> properties. However, the user agent *MUST* always expose global WAI-ARIA states
> and properties to accessibility APIs, even if an element has an explicit
> or inherited role of presentation."
>
>
>
>
> On Jan 26, 2016, at 9:21 AM, Joseph Scheuhammer <clown@alum.mit.edu>
> wrote:
>
> On 2016-01-26 10:14 AM, Joseph Scheuhammer wrote:
>
> These two sentences are slightly garbled.  I think you mean:
>
> "
> Consequently, using a role=“presentation” or role=“none” on an <img>
> element is equivalent to using aria-hidden=“true”. If it is possible to
> make the descendent elements accessible, the user agent SHOULD embed the
> DOM representing those descendants directly within the host document.
> "
>
>
> Another clarification to make it easier for the reader, namely, say how
> role="presentation" and aria-hidden="true" are equivalent in this case:
>
> "
> Consequently, using a role=“presentation” or role=“none” on an <img>
> element is equivalent to using aria-hidden=“true”, where the <img> is not
> exposed to accessibility APIs. If it is possible to make the descendent
> elements accessible, the user agent SHOULD embed the DOM representing those
> descendants directly within the host document.
> "
>
> Or, maybe I'm beating a dead horse.
>
> --
> ;;;;joseph.
>
> 'Die Wahrheit ist Irgendwo da Draußen. Wieder.'
>                 - C. Carter -
>
>
>