Re: svg aam feedback - Amelias changes - part 3

(See also my previous replies to Fred's part 1
<https://lists.w3.org/Archives/Public/public-svg-a11y/2016May/0024.html>
and part 2
<https://lists.w3.org/Archives/Public/public-svg-a11y/2016May/0025.html>)

> *For the changes starting on line 836 in section 5.1.2 Including Elements
> in the Accessibility Tree.*
> List after 3rd paragraph should include the *mesh* element as it is
> treated similar to shapes.
>
Yes. Corrected.  May have to change it back if the SVG working group agrees
to treat mesh as a proper (never-rendered) paint server, but that's an
issue for another day.

> *For the changes starting on line 836 in section 5.1.2 Including Elements
> in the Accessibility Tree.*
>
[clipped]
> Note the SVG 2 spec already defines renderable element
> <https://svgwg.org/svg2-draft/render.html#TermRenderableElement> and I
> would like inclusion rules to take precedence over exclusion rules.
>
I've responded on the general issue of rendered elements elsewhere, not
going to repeat.  However, the definition for "renderable element" is not a
substitute: it would include, for example, an image or shape element even
if it is inside a pattern, symbol, or defs element.


> *For the changes starting on line 967*
>
> Typo, are misspelled
>
corrected

>  In the bullet list
>
> A *rendered*
> <https://svgwg.org/svg2-draft/render.html#TermRenderedElement> element
> with a positive integer value for the tabindex attribute, or which is
> *focusable* <https://svgwg.org/svg2-draft/interact.html#TermFocusable> by
> default and has not been removed from the tab order with a negative integer
> tabindex attribute, which may receive keyboard focus and therefore
> keyboard input events.
> to
> A renderable
> <https://svgwg.org/svg2-draft/render.html#TermRenderableElement> element
> with a tabindex attribute. An element which is *focusable*
> <https://svgwg.org/svg2-draft/interact.html#TermFocusable> by default
> that does not have a negative tabindex attribute and has not been excluded
> from the accessibility tree by other means such as having display none.
>
Again, renderable is not a substitute for rendered. A rendered element,
however, includes any renderable element that "has not been excluded from
the accessibility tree by other means such as having display none".


> *For the changes starting on line 994*
>
> For SVG, this specifically means that elements that would normally be
> included in the accessibility tree except for the fact they are invisible
> (e.g., because of the visibility: hidden style property, or a combination
> of fill: none and stroke: none for shapes or text) should nonetheless be
> included in the accessibility tree if they can receive pointer events based
> on the computed value of the *pointer-events*
> <https://svgwg.org/svg2-draft/interact.html#PointerEventsProperty>
> property.
>
> remove style and file/stroke
>
> For SVG, this specifically means that elements that would normally be
> included in the accessibility tree except for the fact they are invisible
> (e.g., because of the visibility: hidden) should nonetheless be included
> in the accessibility tree if they can receive pointer events based on the
> computed value of the *pointer-events*
> <https://svgwg.org/svg2-draft/interact.html#PointerEventsProperty>
> property.
>
> I haven't made these changes, but I am open to them, as I discussed in the
last email (
https://lists.w3.org/Archives/Public/public-svg-a11y/2016May/0025.html).

However, even if we removed fill & stroke from the hiding criteria, they
would still factor in to the pointer-events property.  They would therefore
still affect whether or not an element with  visibility: hidden is
interactive.