- From: Janina Sajka <janina@rednote.net>
- Date: Wed, 15 Aug 2012 19:45:00 +0000
- To: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- CC: PFWG Public Comments <public-pfwg-comments@w3.org>
Dear Leif Halvard Silli: Thank you for your comments on the 10 January 2012 Last Call Working Draft of WAI-ARIA 1.0 User Agent Implementation Guide (http://www.w3.org/TR/2012/WD-wai-aria-implementation-20120110/). The Protocols and Formats Working Group has reviewed all comments received on the draft. We would like to know whether we have understood your comments correctly and whether you are satisfied with our resolutions. Please review our resolutions for the following comments, and reply to us by 21 September 2012 to say whether you accept them or to discuss additional concerns you have with our response. If we do not hear from you by that date, we will mark your comment as "no response" and close it. If you need more time to consider your acknowledgement, please let us know. We have sent this response shortly before publishing a planned updated draft of the WAI-ARIA 1.0 User Agent Implementation Guide. This document is being returned to ordinary Working Draft because the group found ambiguities in user agent implementation expectations. If your concerns are still open in this document, you may submit a new comment on that version in addition to acknowledging our response to your prior comment. The group intends to respond to all known issues and then publish a second Last Call Working Draft. You can respond in the following ways: * If you have a W3C account, we request that you respond online at http://www.w3.org/WAI/PF/comments/acknowledge?document_version_id=18; * Else, by email to public-pfwg-comments@w3.org (be sure to reference our comment ID so we can track your response). Note that this list is publicly archived. Please see below for the text of comments that you submitted and our resolutions to your comments. Note that if you still strongly disagree with our resolution on an issue, you have the opportunity to file a formal objection (according to 3.3.2 of the W3C Process, at http://www.w3.org/2005/10/Process-20051014/policies.html#WGArchiveMinorityViews) to public-pfwg-comments@w3.org. Formal objections will be reviewed during the candidate recommendation transition meeting with the W3C Director, unless we can come to agreement with you on a resolution in advance of the meeting. Thank you for your time reviewing and sending comments. Though we cannot always do exactly what each commenter requests, all of the comments are valuable to the development of WAI-ARIA 1.0 User Agent Implementation Guide. Regards, Janina Sajka, PFWG Chair Michael Cooper, PFWG Staff Contact Comment 372: Include description URLs (with longdesc as example) in the img role Date: 2012-03-14 Archived at: UNSET Relates to: WAI-ARIA 1.0 User Agent Implementation Guide - 5.4. Role mapping <http://www.w3.org/TR/2012/WD-wai-aria-implementation-20120110/#mapping_role> Status: Proposal not accepted ------------- Your comment: ------------- See, the ARIA draft's description of the 'img' role. The description fails to cover the 'img' role properly: The role description includes pointers to the definition of <img> in the host languages HTML4 and and DTB, both of which can include a longdesc attribute. But despite these examples in the host languages elements, ARIA does no not include or mention longdesc - or 'description URLs' as one could call it more generally - in its description of the 'img' role. In a situation where @longdesc place in HTML5 is contested, this could be interpreted as if even ARIA is contesting the usefulness of @longdesc/description urls. That anyone who opens the one-page version of ARIA, will be able to search and locate 'longdesc', will be very useful. -------------------------------- Response from the Working Group: -------------------------------- @longdesc is an HTML attribute and this is out of scope for the WAI-ARIA User Agent Implementation Guide. Even though we have a few places where HTML-specific information is included, we have tried to minimize it so that the UAIG is applicable to any host language that implements WAI-ARIA. Browsers implementing HTML must expose the @longdesc information to ATs independently of whether or not the element has a WAI-ARIA role or other WAI-ARIA attributes.
Received on Wednesday, 15 August 2012 19:45:03 UTC