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

Dear Philippe Le Hegaret:

Thank you for your comments on the 24 February 2009 Last Call Working
Draft 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 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

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

* Else, 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, and may also
include links to the relevant changes in the Accessible Rich Internet
Applications (WAI-ARIA) 1.0 editors' draft at

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
to 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

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 266: Comment on WAI-ARIA Role
Date: 2009-04-30
Archived at:
Relates to: Accessible Rich Internet Applications (WAI-ARIA) 1.0 <>
Status: Alternate action taken

Your comment:
I've trying to apply WAI ARIA to a video player done in HTML5 [1] and

ran into two questions:

- Are WAI ARIA user agents supposed to track all changes to aria


 I have two examples:

 * aria-label:

  The volume button changes role  depending on its associated popup

slider. When the popup volume slider is visible, it enables the user to

mute or unmute the video. I update the label of the volume button

depending on the visibility of the volume slider.

 * aria-valuemax:

  I update the valuemax of the progressbar and the slider when receiving

a durationchange HTML event from the video (this happens at load time or

if the video is updated).

- I update some parts of the SVG, such as the logo of the play/pause,

depending on the state of the button itself. Since the ARIA functions

associated with the button are attached on a different element (ie the

mostly transparent rectangle in front), should I attach a presentation

role to the logos to ensure that the user agent will ignore those DOM



Response from the Working Group:
We are updating the ARIA specification to clarify that roles must not
change with time or user actions.

For the volume button example we do not believe the button itself should
change role.  When the button is pressed and the new slider becomes visible
on the screen the slider should have role of slider while the volume button
maintains its role.  The volume button should update its label property to
reflect its current state.

With respect to your aria-valuemax question, if we understand you
correctly, you are updating aria-valuemax appropriately with respect to
duration change events.

With respect to your use of role="presentation", it again appears you are
following the spirit of ARIA.  However, since we do not yet have an
implementation of ARIA for SVG, we cannot confirm the details of your

Received on Tuesday, 15 December 2009 00:34:45 UTC