This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13541 - Incomplete accessibility API exposure rules for svg element
Summary: Incomplete accessibility API exposure rules for svg element
Status: CLOSED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Rich Schwerdtfeger
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y, a11ytf
Depends on:
Blocks: 23470
  Show dependency tree / graph
 
Reported: 2011-08-02 22:50 UTC by Matt May
Modified: 2016-03-03 15:31 UTC (History)
12 users (show)

See Also:

Attachments

Description Matt May 2011-08-02 22:50:42 UTC 
There is no information on how SVG content is to be handled by or conveyed to AT.

The following should be present in some form:
What the default ARIA role is for svg; 
Whether setting its role to "application" will offer access to the SVG DOM directly; 
Whether setting its role to something other than "application" would hide any accessibility metadata existing inside the SVG object;
Whether HTML content inside an svg:foreignObject fragment is attached to the HTML DOM.
Comment 1 Anne 2011-08-03 06:46:16 UTC 
Defining the semantics for SVG is out of scope for the HTML specification. It solely defines a syntax for embedding SVG content in HTML. Please take that issue up with the SVG WG.
Comment 2 Henri Sivonen 2011-08-03 06:51:05 UTC 
This doesn't have anything to do with parsing.

Why do you expect to find information about the accessibility characteristics of SVG in the HTML specs as opposed to the SVG spec?
Comment 3 Anne 2011-08-03 07:13:42 UTC 
The writing HTML documents section could be clearer on how you go in and out of the foreign lands. Currently it is not entirely clear that you can escape foreign content.
Comment 4 Michael[tm] Smith 2011-08-04 05:00:35 UTC 
mass-moved component to LC1
Comment 5 Michael[tm] Smith 2011-11-20 18:09:15 UTC 
Matt, this bug is waiting for your response to comment #1 and comment #2:
> Defining the semantics for SVG is out of scope for the HTML specification. It
> solely defines a syntax for embedding SVG content in HTML. Please take that
> issue up with the SVG WG.
[...]
> This doesn't have anything to do with parsing.
> 
> Why do you expect to find information about the accessibility characteristics
> of SVG in the HTML specs as opposed to the SVG spec?
Comment 6 Ian 'Hixie' Hickson 2011-11-24 21:28:56 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: Out of scope for HTML.
Comment 7 Rich Schwerdtfeger 2014-05-01 16:32:45 UTC 
This will be defined the, by the new SVG User Agent Accessibility API Mapping guides (name may change). It will not be an HTML5 issue. So, I verify.