27838 2015-01-15 12:04:29 +0000 merge aria mapping table into role/attribute mapping tables 2015-06-24 08:20:45 +0000 1 1 1 Unclassified ARIA HTML AAM 1.1 PC Windows NT RESOLVED FIXED P2 normal --- 1 faulkner.steve jason faulkner.steve jason schwer surkov.alexander oldest_to_newest 117207 0 faulkner.steve 2015-01-15 12:04:29 +0000 After discussions with Rich S suggest we merge the tables as per the SVG mappings spec. example the a element in svg http://rawgit.com/w3c/aria/master/svg-aam/svg-aam.html#details-id-0 117284 1 jason 2015-01-16 19:23:55 +0000 I'm happy to take this one, but I don't understand what the merged table would look like. Can you provide an example for a few rows using an element whose mapping is covered by an existing ARIA role, and one (e.g. <canvas>) whose mapping varies between the acc APIs and doesn't map one-to-one with any role listed in Core-AAM? 117351 2 faulkner.steve 2015-01-20 13:38:09 +0000 (In reply to Jason Kiss from comment #1) > I'm happy to take this one, but I don't understand what the merged table > would look like. Can you provide an example for a few rows using an element > whose mapping is covered by an existing ARIA role, and one (e.g. <canvas>) > whose mapping varies between the acc APIs and doesn't map one-to-one with > any role listed in Core-AAM? Hi Jason, the existing nonARIA mappings in the second table would remain as is. a row which has an ARIA mapping - example: a (represents a hyperlink) WAI-ARIA link MSAA + UIA Express Use WAI-ARIA mapping MSAA + IAccessible2 Use WAI-ARIA mapping UIA Use WAI-ARIA mapping ATK Use WAI-ARIA mapping AX Use WAI-ARIA mapping sound OK? 117360 3 jason 2015-01-20 18:32:45 +0000 That should work. I wondered if it was a little repetitive for those elements with ARIA mappings, hence the two tables initially, but having all elements in a single table will also be good. 117651 4 jason 2015-02-02 03:16:12 +0000 Done: https://github.com/w3c/aria/commit/d67d285f63e0a9ef2565ecec1bd4b1dfb1c1c78c#diff-9740bd6e9e07dccd175e4980cde62444