- From: Richard Schwerdtfeger <schwer@us.ibm.com>
- Date: Mon, 16 Mar 2015 14:58:46 -0500
- To: "Erik Dahlström" <ed@opera.com>
- Cc: public-svg-a11y@w3.org
- Message-ID: <OF185B1E05.B148E60A-ON86257E0A.006C4D05-86257E0A.006DC037@us.ibm.com>
Hi Erik, I updated the <desc> and <title> secton of the spec.: https://svgwg.org/svg2-draft/struct.html#DescriptionAndTitleElements There was a restriction in the text which I did not modify: "Alternate presentations are possible, both visual and aural, which display the ‘desc’ and ‘title’ elements but do not display ‘path’ elements or other graphics elements." Why should this be restriction on path or other graphics elements? I did not close issues 24, 24, 25 on the page. Please take a look at the section and see if you think I need to make any more changes to be able to close those issues. I did not explain the precedence for when aria-labelledby and aria-label over title. The ARIA name computation specification defines the precedence when mapping to platform accessibility APIs but, as the text states, <title> should only be used for tooltips and and not the aria attributes. I think the purposes of these attributes is now clearer for authors. aria-describedby takes precedence over <desc> on an element when determining a description. I also updated all the ARIA links which apparently had changed in the lates ARIA 1.1 draft. The spec. now references the SVG Accessibility Mapping specification now that the FWPD is out there. One suggestion from the task force is that we put more authoring guidance, only, in a separate authoring guide in the <title> and <desc> section. Rich Rich Schwerdtfeger
Received on Monday, 16 March 2015 19:59:53 UTC