This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
WRT the SVG element mapping table [1], find the "Platform WAI-ARIA Role Mappings for each WAI-ARIA Role Applied" column header and the values in that column a little confusing. The values in that column are either: A. one or more ARIA roles linked to their mappings in the Core-AAM spec, e.g. the entry for iframe [2] B. a link, "Role Mappings", that links to the Core-AAM role mapping table C. a note that "No role may be applied." I've no issues with A or C above, though they suggest that a column header like "Applicable WAI-ARIA role mappings" or "Alternative WAI-ARIA role mappings" or similar might be clearer. Does "Role Mappings" (item B above) mean that any WAI-ARIA role may be applied, or something else? Would "Any WAI-ARIA role" or "All WAI-ARIA roles" be clearer? I've likely just gotten comfortable with the Core-AAM and HTML-AAM mapping tables, but I'm wondering if revisiting the SVG mapping table's structure as a whole would be helpful? For example, what if the table had the following columns: -SVG Element -Default WAI-ARIA role -Alternative WAI-ARIA roles (or some similar but better phrase) -Accessibility API Mapping The cells in the "Default WAI-ARIA role" column would have a link to the applicable ARIA role, or say "No corresponding role". The cells in the "Alternative WAI-ARIA roles" column would list and link to any other applicable ARIA roles, or say something like "No other roles may be applied". And the "Accessibility API Mapping" column would have something like "Use WAI-ARIA mapping" where there's a default ARIA role for the SVG element, or "Not mapped". Or, where a certain AAPI uses a different mapping, e.g. the video element [3], something like "Use WAI-ARIA mapping, except ATK/ATSPI that maps to role ATK_ROLE_VIDEO". IMO, I think this would clarify the mapping definitions for each element, and also align this table more closely with the structure of the current Core-AAM and HTML-AAM mapping tables, which I think is important given that the AAM documents are suite of specifications. [1] http://rawgit.com/w3c/aria/master/svg-aam/svg-aam.html#mapping_role_table [2] http://rawgit.com/w3c/aria/master/svg-aam/svg-aam.html#role-map-iframe [3] http://rawgit.com/w3c/aria/master/svg-aam/svg-aam.html#role-map-video