W3C home > Mailing lists > Public > public-pfwg-comments@w3.org > January to March 2013

Response to your comments on WAI-ARIA 1.0 Authoring Practices

From: Janina Sajka <janina@rednote.net>
Date: Tue, 26 Feb 2013 14:58:06 +0000
Message-Id: <E1UALyo-0002h7-Hv@tibor.w3.org>
To: Carolyn MacLeod <Carolyn_MacLeod@ca.ibm.com>
CC: PFWG Public Comments <public-pfwg-comments@w3.org>
Dear Carolyn MacLeod:

Thank you for your comments on the 16 September 2010 Working Draft of
WAI-ARIA 1.0 Authoring Practices
(http://www.w3.org/TR/2010/WD-wai-aria-practices-20100916/). 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 8 March 2013 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. You can
respond in the following ways:

* If you have a W3C account, we request that you respond online at

* 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

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 Authoring
Practices editors' draft at http://www.w3.org/WAI/PF/aria-practices/.

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
to public-pfwg-comments@w3.org. Formal objections will be reviewed with the
Director before the document is finalized as a Working Group Note, unless
we can come to agreement with you on a resolution in advance of the

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 Authoring Practices.


Janina Sajka, PFWG Chair
Michael Cooper, PFWG Staff Contact

Comment 359: Comment on WAI-ARIA 1.0 Authoring Practices document
Date: 2011-10-03
Archived at: http://lists.w3.org/Archives/Public/public-pfwg-comments/2011OctDec/0000.html
Relates to: WAI-ARIA 1.0 Authoring Practices - 2.  General Steps for Building an Accessible Widget with WAI-ARIA <http://www.w3.org/TR/2010/WD-wai-aria-practices-20100916/#accessiblewidget>
Status: Accepted proposal

Your comment:
On the following page: http://www.w3.org/TR/wai-aria-practices/ In section
2. General Steps for Building an Accessible Widget with  WAI-ARIA
(http://www.w3.org/TR/wai-aria-practices/#accessiblewidget) In point 3.
Establish the widget structure in the markup (parent/child) There is an
example that has the following markup:

<div role="toolbar" tabindex="0" aria-activedescendant="button1">
  <img src="buttoncut.png" alt="cut" id="button1">
  <img src="buttoncopy.png" alt="copy" id="button1">
  <img src="buttonpaste.png" alt="paste" id="button1">

I believe that you do not want to have three identical id's ("button1"). 

Response from the Working Group:
We have corrected these IDs.
Received on Tuesday, 26 February 2013 14:58:12 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:01:03 UTC