13541 2011-08-02 22:50:42 +0000 Incomplete accessibility API exposure rules for svg element 2016-03-03 15:31:23 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified PC Windows XP CLOSED FIXED a11y, a11ytf P2 normal --- 23470 1 mattmay schwer annevk chaals cooper everett faulkner.steve hsivonen ian laura.lee.carlson mike public-html-a11y public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 52028 0 mattmay 2011-08-02 22:50:42 +0000 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. 52118 1 annevk 2011-08-03 06:46:16 +0000 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. 52121 2 hsivonen 2011-08-03 06:51:05 +0000 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? 52128 3 annevk 2011-08-03 07:13:42 +0000 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. 52349 4 mike 2011-08-04 05:00:35 +0000 mass-moved component to LC1 60232 5 mike 2011-11-20 18:09:15 +0000 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? 60446 6 ian 2011-11-24 21:28:56 +0000 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. 104910 7 schwer 2014-05-01 16:32:45 +0000 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.