- From: Johannes Koch <koch@w3development.de>
- Date: Tue, 26 Feb 2013 22:58:05 +0100
- To: PFWG Public Comments <public-pfwg-comments@w3.org>
Dear Janina, see (short) response below Am 26.02.2013 15:58, schrieb Janina Sajka: > Dear Johannes Koch: > > 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 > http://www.w3.org/WAI/PF/comments/acknowledge?document_version_id=10; > > * 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 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 > http://www.w3.org/2005/10/Process-20051014/policies.html#WGArchiveMinorityViews) > 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 > 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 Authoring Practices. > > Regards, > > Janina Sajka, PFWG Chair > Michael Cooper, PFWG Staff Contact > > > Comment 351: aria-haspopup > Date: 2010-11-17 > Archived at: http://lists.w3.org/Archives/Public/public-pfwg-comments/2010OctDec/0015.html > Relates to: WAI-ARIA 1.0 Authoring Practices - Menu (widget)<http://www.w3.org/TR/2010/WD-wai-aria-practices-20100916/#menu> > Status: Accepted proposal > > ------------- > Your comment: > ------------- > in "WAI-ARIA 1.0 Authoring Practices", section 10 -> menu > (<http://www.w3.org/TR/wai-aria-practices/#menu>) > > Table "Characteristics", row "WAI-ARIA Roles, States, and Properties:", > second cell, third bullet: > >> If activation of your menuitem produces a popup menu, then the menuitem > should have aria-haspopup set to the ID of the corresponding menu to allow > the assistive technology to follow the menu hierarchy and assist the user > in determining context during menu navigation. > > According to > <http://www.w3.org/TR/wai-aria/states_and_properties#aria-haspopup> > > the value of the aria-haspopup property is true or false. Should one use > the aria-controls property > (<http://www.w3.org/TR/wai-aria/states_and_properties#aria-controls>) set > to the ID of the corresponding menu? > > <li role="menuitem" aria-expanded="true" aria-haspopup="true" > aria-controls="menu01">File > <ul role="menu" id="menu01"> > <li role="menuitem">Open</li> > <!-- ... --> > </ul> > </li> > > -------------------------------- > Response from the Working Group: > -------------------------------- > We have changed the text to read: > > If activation of your menuitem produces a popup menu, then the menuitem > should have aria-haspopup set to "true" so that an assistive technology > knows that the menuitem has a sub menu. I'm fine with the change. > To answer your question about aria-controls, it is unnecessary to set the > controls relationship between the menuitem and the popup menu. Since these > are popup windows the ATs are also tracking system events to track the > menu/submenu hierarchy. Consequently there was no need to use and ID for > aria-haspopup or the controls relationship to establish the relationships > between menus. Thanks for the explanation. -- Johannes Koch In te domine speravi; non confundar in aeternum. (Te Deum, 4th cent.)
Received on Tuesday, 26 February 2013 21:55:03 UTC