Response to your comments on WAI-ARIA 1.0 User Agent Implementation Guide

Dear Loretta Guarino Reid:



Thank you for your comments on the 24 February 2009 First Public Working
Draft of WAI-ARIA 1.0 User Agent Implementation Guide
(http://www.w3.org/TR/2009/WD-wai-aria-implementation-20090224/). 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 1 February 2010 to say whether you accept them or to discuss additional
concerns you have with our response. 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=5;



* 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. Each comment includes a link to the archived
copy of your original comment on
http://lists.w3.org/Archives/Public/public-pfwg-comments/, and may also
include links to the relevant changes in the WAI-ARIA 1.0 User Agent
Implementation Guide editors' draft at
http://www.w3.org/WAI/PF/aria-implementation/20091214/.



Due to the scope of changes made in response to comments on the Last Call
Working Draft of WAI-ARIA, we are returning the specification to Working
Draft status. We will shortly publish a public "stabilization draft" of
WAI-ARIA and updated Working Drafts of the accompanying documents. While
these versions will not incorporate further discussion based on your
acknowledgement of our response to your comments, we will work with you on
your feedback as part of our preparation for the following version. You are
also welcome to submit new comments on the new public versions in addition
to sending your acknowledgement of our response to your previous 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 203: Removing object doesn't remove descendants
Date: 2009-04-16
Archived at: http://lists.w3.org/Archives/Public/public-pfwg-comments/2009AprJun/0065.html
Relates to: WAI-ARIA 1.0 User Agent Implementation Guide - 1.2. Accessible tree vs. DOM tree - what's the relation? <http://www.w3.org/TR/2009/WD-wai-aria-implementation-20090224/#intro_treetypes>
Status: Accepted proposal

-------------
Your comment:
-------------
This section needs to elaborate that removing an object from the
accessibility hierarchy does not mean removing all of its descendants. Only
the object is elided, and its children appear as children of its parent. In
particular, we think the following sentence is wrong: "Objects that should
be removed from the accessible hierarchy (including their descendants):"
since this would imply that none of the contents of a layout (presentation)
table would be exposed to AT. 

--------------------------------
Response from the Working Group:
--------------------------------
The UAIG text has been modified to clarify that descendants of tables which
represent the text content are not removed from the tree. The structural
elements will be removed as it wouldn't make sense to have table cells in
the tree without their owning parent. But the text content is not removed
and will continue to be a descendant of the owning table's parent. 



Note that the text in question contains normative rules which are
inappropriate for the Introduction. This text has been moved to section 4.1
and is available from
http://www.w3.org/WAI/PF/aria-implementation/20091214/#mapping_general.

Received on Tuesday, 15 December 2009 00:28:44 UTC