534873 - (svga11y) [meta] SVG a11y

Status: NEW

(Core :: Disability Access APIs, defect)

Comment 2

[alexander :surkov (:asurkov)]

from bug 809744:

SVG has title and desc elements (http://www.w3.org/TR/SVG/struct.html#DescriptionAndTitleElements) which should be mapped into accessible name and accessible description correspondingly.

SVG element containing these elements should be accessible. It makes sense to expose an accessible for title element since it's implemented as tooltip and fire proper events when it shown/hidden.

Some SVG elements use xlink attributes. I'm not sure whether they act as links.

Also SVG has text element which is visible and thus should be exposed to AT as text interface.

Maybe we have something else that should be accessible.

SVG example which is not accessible in Firefox at all: http://www.nvaccess.org/audioScreen/svg/house.svg.

Jonathan, can you provide some details about SVG and SVG implementation please? For example, what elements can contain title and desc elements and where their implementation is located in.

Comment 3

[Michael Curran]

I would personally like to see that:
 * Any svg element with an inner title or desc be exposed as an Accessible object, who's name is title and description is desc. Role can most likely be graphic.
 * accNavigate should work, but most important is accHitTest as accessing svgs with touch screens by the blind has major practical benefits.
 * a nice-to-have though not so critical is general support for ARIA. I.e. ability to hide an svg element from the accessible tree with role="presentation". I have used this to an extent in my house.svg example linked in the bug.

Comment 4

[alexander :surkov (:asurkov)]

Jonathan, I'd be nice if you can advice us about svg implementation

Comment 5

[alexander :surkov (:asurkov)]

Jonathan, I'd be nice if you can advice us about svg implementation

Comment 6

[Jonathan Watt [:jwatt]]

(In reply to alexander :surkov from comment #2)
> from bug 809744:
> 
> SVG has title and desc elements
> (http://www.w3.org/TR/SVG/struct.html#DescriptionAndTitleElements) which
> should be mapped into accessible name and accessible description
> correspondingly.
> 
> SVG element containing these elements should be accessible. It makes sense
> to expose an accessible for title element since it's implemented as tooltip
> and fire proper events when it shown/hidden.

That sounds like it makes sense.

> Some SVG elements use xlink attributes. I'm not sure whether they act as
> links.

Depends on what you mean by "links". I think you only need to care about <a xlink:href="blah"></a>.

> Also SVG has text element which is visible and thus should be exposed to AT
> as text interface.

Note that bug 655877 is radically changing the SVG text implementation. Best not to touch that code until that bug is fixed.

> Maybe we have something else that should be accessible.
> 
> SVG example which is not accessible in Firefox at all:
> http://www.nvaccess.org/audioScreen/svg/house.svg.
> 
> Jonathan, can you provide some details about SVG and SVG implementation
> please? For example, what elements can contain title and desc elements and
> where their implementation is located in.

The section of the spec you linked to says these elements can contain <title>/<desc>:

http://www.w3.org/TR/SVG/intro.html#TermContainerElement
http://www.w3.org/TR/SVG/intro.html#TermGraphicsElement

The implementation of these elements is under content/svg/content/src in files with names matching the element names.