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

Dear Janina Sajka:

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 364: elements with @hidden must not be included in the a11y tree
Date: 2012-03-04
Archived at: http://lists.w3.org/Archives/Public/public-pfwg-comments/2012JanMar/0012.html
Relates to: WAI-ARIA 1.0 User Agent Implementation Guide - 5.1.1. Including Elements in the Accessibility Tree <http://www.w3.org/TR/2012/WD-wai-aria-implementation-20120110/#include_elements>
Status: Answered question

-------------
Your comment:
-------------
This comment was forwarded to the comments list by Janina Sajka to trigger
PFWG processing of a set of issues related to HTML implementation of ARIA.

http://www.w3.org/WAI/PF/aria-implementation/#include_elements

This confirms that elements with @hidden must not be included in the  a11y
three. The HTMLwg is in violent *agreement* with ARIA on this, as  much as
I can see. 

--------------------------------
Response from the Working Group:
--------------------------------
Any host language native semantic for hidden (display:none,
visibility:hidden, HTML5 @hidden) that states that an element is hidden,
the element and its descendants MUST NOT appear in the accessibility tree.
An element that is hidden solely through the provision of an aria-hidden
attribute set to "true" SHOULD NOT be exposed as an object in the
accessibility tree. The exclusion in the accessibility tree includes its
descendants.

----------------------------------------------------------------------


Comment 365: aria-describedby exposes semantics
Date: 2012-03-04
Archived at: http://lists.w3.org/Archives/Public/public-pfwg-comments/2012JanMar/0012.html
Relates to: WAI-ARIA 1.0 User Agent Implementation Guide - 5.6.3.2. Reverse Relations <http://www.w3.org/TR/2012/WD-wai-aria-implementation-20120110/#mapping_additional_relations_reverse_relations>
Status: Declined to process

-------------
Your comment:
-------------
This comment was forwarded to the comments list by Janina Sajka to trigger
PFWG processing of a set of issues related to HTML implementation of ARIA.

http://www.w3.org/WAI/PF/aria-implementation/#mapping_additional_relations_reverse_relations

This seems quite important - so I quote:

    "Note that aria-describedby may reference structured or interactive 
information where users would want to be able to navigate to different 
sections of content. User agents MAY provide a way for the user to 
navigate to structured information referenced by aria-describedby and 
assistive technology SHOULD provide such a method."

This quote *does* say that AT/UA should make available to the user the 
interactive and structured semantics of an section that  aria-describedby
points to. 

--------------------------------
Response from the Working Group:
--------------------------------
Thank you for your comment. This comment arrived after the deadline to
submit comments and we were unable to complete it for this draft. We plan
to address it before publishing the Last Call draft.

Received on Wednesday, 15 August 2012 19:45:01 UTC