- From: Richard Schwerdtfeger <schwer@us.ibm.com>
- Date: Sat, 19 Jun 2010 07:09:19 -0500
- To: Steven Faulkner <faulkner.steve@gmail.com>
- Cc: cyns@exchange.microsoft.com, public-html-a11y@w3.org
- Message-ID: <OFFF775E97.1F3ABA9F-ON86257747.0041B008-86257747.0042C554@us.ibm.com>
Rich Schwerdtfeger CTO Accessibility Software Group Steven Faulkner <faulkner.steve@gmail.com> wrote on 06/17/2010 04:06:33 PM: > From: Steven Faulkner <faulkner.steve@gmail.com> > To: Richard Schwerdtfeger/Austin/IBM@IBMUS > Cc: cyns@exchange.microsoft.com, public-html-a11y@w3.org > Date: 06/17/2010 04:07 PM > Subject: Re: review of section 3.2.6 ARIA roles and properties in > HTML first detailed pass > > hi rich thanks for the feedback > > >You have img element with an empty alt attribute but img does not > reside in the second table. An image could easily be >overridden. > >Why are <div> and <span> not included in the language features? > > > as per the current tables in the html5 spec if an element has no > restrictions placed on it in regards to its role, the element is not > included in either table. > > #I will add a list of elements that have no restrictions to make > this explicit. > Great! It will also be good to see this to see if we have missed something. Do you think this set should ultimately reside in an appendix? > > >Where do we call out global ARIA attributes? - these can be used > anywhere per the ARIA spec. > As far as aria-* attrubutes are concerned all are allowed on any > element unless otherwise stated. > > #I will make this clear as well. > Great! I think that would be an improvement to what we have. > >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. > see preceding comment. > That's fine but the wording that haspopup only applies to a context menu should be corrected to include submenus. Two examples: - menu sub menu - drop down buttons > >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. > will ad nav to section > the main restriction is as per the aria spec. > > >What happened to <th>? It should have a default role of either > columnheader but can be overriddent by rowheader or >columnheader > > its in table 1 > The overrides for this should include columenheader and rowheader. These are specific semantics. > >footer has a default role of contentinfo. If you recall Ian or > someone said footer has no defined location. > this mapping is taken from the current html5 spec text. > The HTML 5 spec is wrong then. We should correct it. BTW. Nice job on the mapping tables. > regards > > steve > > On 17 June 2010 21:35, Richard Schwerdtfeger <schwer@us.ibm.com> wrote: > 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 > > > > -- > with regards > > Steve Faulkner > Technical Director - TPG Europe > Director - Web Accessibility Tools Consortium > > www.paciellogroup.com | www.wat-c.org > Web Accessibility Toolbar - http://www.paciellogroup.com/resources/ > wat-ie-about.html
Received on Saturday, 19 June 2010 12:09:55 UTC