Review of March 7, 2013 Using WAI-ARIA in HTML draft

Steve,

Nice document! I did a quick review.

https://dvcs.w3.org/hg/aria-unofficial/raw-file/tip/index.html

Section 2.3

I would note that in some mobile browsers keyboard function may not be
available to all elements. Until this problem is corrected additional
interactive controls may be required to control an element with the
keyboard.

Section 2.7

role="presentation"

I would change "For elements with required children (such as ul or table)
any required child elements nested inside the element with
role=presentation also have their semantics removed."

For elements with required descendants (such as ul or table) any required
descendant elements nested inside the element with role=presentation also
have their semantics removed. This deals with required children of
children.

and later change:

Any elements that are not required children of the element with a
role=presentation keep their semantics. This includes other elements with
required children.

to:

Any elements that are not required descendants of the element with a
role=presentation keep their semantics. This includes other elements with
required descendants.

Your examples are great.

Section 2.9

I recommend making this section role="application" and role="document"  and
go greater detail into role="document"

Create a section called landmarks and state that all content MUST reside in
a landmark to ensure users navigating with landmarks do not miss orphaned
content. I would suggest creating a Matrix showing the HTML5 element and
ARIA role that can be used interchangeably.  I would also include the main
element in that list.

Rich