- From: Fred Esch <fesch@us.ibm.com>
- Date: Tue, 29 Mar 2016 07:14:45 -0500
- To: Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com>
- Cc: SVG-A11y TF <public-svg-a11y@w3.org>
- Message-Id: <201603291300.u2TD05pK016436@d01av04.pok.ibm.com>
Adding to agenda on Wednesday. Agenda Round the table, news, additions for the agenda Open Actions Action Review Role mapping for SVG ARIA 1.1 testing Mac and Linux threads https://lists.w3.org/Archives/Public/public-svg-a11y/2016Mar/0051.html https://lists.w3.org/Archives/Public/public-svg-a11y/2016Mar/0049.html https://lists.w3.org/Archives/Public/public-svg-a11y/2016Mar/0047.html Testable statements wiki pages (with tables) https://www.w3.org/wiki/SVG_Accessibility/Testing/Test_Assertions_with_Tables https://www.w3.org/wiki/SVG_Accessibility/Testing/Test_Assertions/Language_Tables test file zips (JSON for test harness and directories of test files) All tests not lang dependent https://www.w3.org/wiki/File:SvgTests.zip Language dependent tests https://www.w3.org/wiki/File:TestLang.zip Regards, Fred Esch Watson, IBM, W3C Accessibility IBM Watson Watson Release Management and Quality From: Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com> To: SVG-A11y TF <public-svg-a11y@w3.org> Date: 03/28/2016 11:39 PM Subject: Coordinating <svg> role mappings between SVG-AAM and HTML-AAM I was looking up HTML element role mappings and noticed that the HTML Accessibility API Mapping spec includes mappings for <svg>: https://w3c.github.io/aria/html-aam/html-aam.html#el-svg Two things worth noting: That spec does not map <svg> to any existing ARIA role It does, however, map it to the relevant graphics-related roles in each API (or group if no appropriate role exists) In contrast, in the SVG-AAM, we have a generic mapping to ARIA "group" with a note that it will eventually be replaced with one of the ARIA graphics roles. The note also states that "further work is required" to determine appropriate mappings for each API. https://rawgit.com/w3c/aria/master/svg-aam/svg-aam.html#role-map-svg So, things to do: As a start, adopt the platform-specific mappings from the HTML-AAM, pending corrections and changes as we develop the Graphics Mapping spec. Coordinate with the HTML-AAM editors to make sure their spec matches ours (or ideally, defers to ours) once that change is made. I really don't want to encourage implementers to use "group" mappings for SVG elements if better options are available. It's just too confusing for screen reader users, and isn't particularly useful for any other AT. The current graphics mapping proposal is not much better, using generic "document" roles. http://rawgit.com/w3c/aria/master/graphics-aam/graphics-aam.html#mapping_role_table If APIs have roles that convey the graphical nature of content while also allowing child content to be explored, those should be used for <svg>. I don't know enough about the APIs and their roles available to know whether the mappings from HTML-AAM are the best choices. But this needs to be sorted out in highest priority so that implementers have something to go on. ~ABR
Attachments
- image/gif attachment: 0F292666.gif
- image/gif attachment: graycol.gif
Received on Tuesday, 29 March 2016 13:00:46 UTC