W3C home > Mailing lists > Public > public-html@w3.org > September 2009

Re: aria vs native alternatives [was: Re: feedback requested on WAI CG Consensus Resolutions on Text alternatives in HTML 5 document]

From: Richard Schwerdtfeger <schwer@us.ibm.com>
Date: Thu, 3 Sep 2009 10:56:37 -0500
To: Henri Sivonen <hsivonen@iki.fi>
Cc: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>, Steven Faulkner <faulkner.steve@gmail.com>, HTMLWG WG <public-html@w3.org>, W3C WAI-XTECH <wai-xtech@w3.org>, wai-xtech-request@w3.org
Message-ID: <OFE6C29CD2.0F5C0C9C-ON86257626.0056AFF9-86257626.0057948A@us.ibm.com>

This is not a contradiction in ARIA principles. Today assistive
technologies are benefiting by being able to produce landmark navigation
interfaces like this.

What you are suggesting is that browser should not take advantage of curb
cuts. We don't mandate that they provide this type of navigation support
but frankly we believe this is a usability curb cut they can take advantage

I can't imagine you would want the city maintenance people to start filling
in the curb cuts and force you to slam your roller bag into them. :-)

I would love a command on my IPhone to bring the navigation sections into
view instead of thumbing my way through the UI.

Product developers benefit from landmarks much the same way they will
benefit from the nav element in HTML 5. They can dump the skip to main
content link which messes with the layout of their UI. Now an advantage of
ARIA is that if you wanted to bring up the navigational land marks or HTML
5 landmark tags in a navigational tree view you can declaratively label
each with a heading that can be displayed next to it.


Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist

             Henri Sivonen                                                 
             Sent by:                                                   To 
             wai-xtech-request         Steven Faulkner                     
             @w3.org                   <faulkner.steve@gmail.com>          
                                       Benjamin Hawkes-Lewis               
             09/03/2009 03:41          <bhawkeslewis@googlemail.com>,      
             AM                        HTMLWG WG <public-html@w3.org>, W3C 
                                       WAI-XTECH <wai-xtech@w3.org>        
                                       Re: aria vs native alternatives     
                                       [was: Re: feedback requested on WAI 
                                         CG Consensus Resolutions on Text  
                                       alternatives in HTML 5 document]    

On Sep 3, 2009, at 00:02, Steven Faulkner wrote:

> "There are also mainstream benefits of providing navigation
> landmarks. Your browser may assign key sequences to move focus to
> these sections as they can be set on every site. Navigation to these
> landmarks is device independent. A personal digital assistant (PDA)
> could assign a device key to get to them in your document."
> http://www.w3.org/WAI/PF/aria-practices/#kbd_layout

This seems to contradict the stated principles of ARIA. I think either
aria-practices or ARIA 1.0 needs to change to remove the contradiction.

Henri Sivonen

(image/gif attachment: graycol.gif)

(image/gif attachment: pic01169.gif)

(image/gif attachment: ecblank.gif)

Received on Thursday, 3 September 2009 15:58:00 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:51 UTC