WAI-ARIA Last Call comments

Following are eleven WAI-ARIA last call comments:

1. Global change: ARIA to WAI-ARIA

2. Regarding the following statement: "Often, heading elements will be 
referenced with the aria-labelledby attribute of the section for which 
they serve as a heading. If headings are organized into a logical outline, 
the aria-level attribute may be used to indicate the nesting level."  Will 
this cause a screen reader to double speak a heading?

3. Regarding the following statement: "Note: Because document and 
application elements can be nested in the DOM, they may have multiple main 
elements as DOM descendants, assuming each of those is associated with 
different document nodes, either by a DOM nesting (e.g., document within 
document) or by use of the aria-owns attribute."  How AT deal with 
duplicate main landmarks?

4. Regarding the following text: "marquee (role)
A type of live region where non-essential information changes frequently. 
Also see log.
Common usages of marquee include stock tickers and ad banners. An example 
of a marquee is a stock ticker. The primary difference between a marquee 
and a log is that logs usually have a meaningful sequence of more 
important content changes."  What is the politeness level?

5. Regarding the menu role, should the separator and group roles be 
discussed here as well?

6. For the following example:
<div role="img" aria-labelledby="caption">
  <img src="example.png" role="presentation" alt="">
  <p id="caption">A visible text caption labeling the image.</p>
</div>

Does a screen reader double speak "A visible text caption labeling the 
image" - once for the image and again as the paragraph is navigated to? 

7. The region role says a region SHOULD have a heading provided an element 
with a heading role.  Shouldn't the first choice be an HTML heading?

8. colheader/rowheader role - Some data tables cells span multiple rows or 
columns and the table "headers" and "id" attributes are used to associate 
cells with specific headings. Complex data tables require additional 
markup to explicitly associate the heading with the data. In the data 
cells, the headers attribute is used on the td element to specify which 
heading cell, via the id attribute on the th element, is associated with a 
specific data cell.  Does ARIA provide support for column and row headings 
that span multiple columns and rows?  As I mentioned, HTML tables provide 
the id and headers attributes.

9. Under the aria-relevant (property), it says "text is added or removed 
from the DOM".  Should this sentence be deleted? How is adding or removing 
a DOM text node different from other notes (mentioned directly above the 
sentence about adding/removing text)?

10. Regarding the following statement: "If the tree is not completely 
represented in the DOM at all times, don't use either the structured or 
aria-owns methods. Instead use aria-level, aria-posinset and 
aria-setsize."   How does one know if the tree is completely represented 
in the DOM at all times?

11. Regarding the following statement: "If the tree is not completely 
represented in the DOM at all times, don't use either the structured..." 
What is the structured method? Is this what was described above in the 
code sample for a tree (directly above this text)? If so, refer back to 
that code sample. 



David Todd
IBM Human Ability & Accessibility Center
http://w3.ibm.com/able 
336-768-2259