Response to your comments on Accessible Rich Internet Applications (WAI-ARIA) 1.0

Dear Takahiro Inada:

Thank you for your comments on the 18 January 2011 Candidate Recommendation
of Accessible Rich Internet Applications (WAI-ARIA) 1.0
( 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 27 January 2014 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 by email to (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

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 Formal objections will be reviewed during
the proposed recommendation transition meeting with the W3C Director,
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 Accessible Rich Internet Applications
(WAI-ARIA) 1.0.


Janina Sajka, PFWG Chair
Michael Cooper, PFWG Staff Contact

Comment 363: We require a property that is only used for explaining how to operate with keyboard.
Date: 2012-02-21
Archived at: UNSET
Relates to: Accessible Rich Internet Applications (WAI-ARIA) 1.0 - 6.6. Definitions of States and Properties (all aria-* attributes) <>
Status: Alternate action taken

Your comment:
Hello WG members,
I often design multifunctional web applications at work. Screen reader
users should be informed how to operate individual UI elements or blocks as
necessary when the focus is on those elements or blocks. Users highly
likely know how to operate the keys for such widgets that can be defined
under the roles of WAI-ARIA-for example TabPanel and Tree-because they are
widely used. However, it is difficult to build a feature- multifunctional
RIA using only the widgets defined in WAI-ARIA. Therefore, uncommon key
operations are sometimes required in order to make all functions operable
via a keyboard. Customizing a widget often not only makes the key operation
unclear, but also confuses users due to the difference between the key
operation detected by users or screen readers and the actual operation.
We have no choice but to use aria-describedby property to describe the
guidance of keyboard operation when that operation is not well known by
users. But, aria-describedby property is essentially intended as
supplements to labels. So, users cannot know just for a keyboard guidance.
They will be forced to be shown a guidance of key operations with
irrelevant information.

Response from the Working Group:
We will consider this for ARIA 1.1. We track this in our issue 631

Received on Tuesday, 21 January 2014 00:24:24 UTC