review of section 3.2.6 ARIA roles and properties in HTML first detailed pass

Review of:
http://www.paciellogroup.com/blog/misc/HTML5/aria-html5-proposal.html

Comments:

Table 1:

<img>

You have img element with an empty alt attribute but img does not reside in
the second table. An image could easily be overridden. For example a
button"
<img alt"ok" src="" role="button" aria-pressed="true" tabindex="0".../>

We should have img in table 2 as well.

Hidden attribute - aria-hidden="true" as the default semantics

<hr> Should we allow the author to establish aria-controls relationships?

There are three commands who have roles of menuitem. I am surprised they
don't have a submenu. Did they not think of that? If so, this is a place
where you will need ARIA as the host language does not support submenus.
Developers can override this with script.  So, I would suggest that we
allow aria-haspopup on these. That raises another issue. This proposal
states that aria-haspopup only refers to a context menu. That may not be
true. It could be a submenu reference.

Table 2:

section: We need to include navigation in what can override. Also, I don't
believe we should restrict role=Main to one per container element. Within a
container you may have subcontainers.

table: This does not have a default role of grid. It can be overridden by a
grid. It has no implied ARIA semantics.

What happened to <th>? It should have a default role of either columnheader
but can be overriddent by rowheader or columnheader

footer has a default role of contentinfo. If you recall Ian or someone said
footer has no defined location.


Why are <div> and <span> not included in the language features?

Where do we call out global ARIA attributes? - these can be used anywhere
per the ARIA spec.

Before I do another pass I'd like to hear feedback on these.

Rich


Rich Schwerdtfeger
CTO Accessibility Software Group