SVG AAM

I updated the document.

I felt we should keep the Accessibility API section but I dramatically
simplified it. The core group could benefit from a similar undertaking.

I modified the section on Excluding Elements from the Accessibility tree to
reference the mapping table (reducing its size) but I also modified the
mapping table to replace not mapped with no accessible object created. It
was clear we need to differentiate not creating a corresponding accessible
object from the tree from how we impact the accessible name and
description.

I am going to take up the discussion about hidden elements with the
core-aam team. There is a fundamental difference over HTML where attributes
are limited to being applied on elements wheeas in SVG these can be child
elements such as in <desc> and <tittle>. These are really attributes more
than they are "programmatically hidden" content such as when display:none
is applied. Thanks for flagging that Amelia.

http://rawgit.com/w3c/aria/master/svg-aam/svg-aam.html

I also removed references to UIA Express. This API has been abandoned with
IE 11 and no further work is being done on it or IE itself in terms of
accessibility. We will focus on UIA for Edge. AT vendors can access the SVG
markup from the DOM like they do with IE today.

I would like to do a heartbeat draft soon. There have been extensive
modifications from the first draft earlier this year.

Rich


Rich Schwerdtfeger