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

hi henri,

>This seems to contradict the stated principles of ARIA.

how so? in the ARIA spec intro it states:

"WAI-ARIA introduces navigation landmarks through its taxonomy and the
XHTMLrole landmarks, which helps persons with dexterity and vision
impairments by
providing for improved keyboard navigation. WAI-ARIA may also be used to
assist persons with cognitive learning disabilities. The additional
semantics allow authors to restructure and substitute alternative content as
needed."
http://www.w3.org/WAI/PF/aria/#intro

regards
Stevef

2009/9/3 Henri Sivonen <hsivonen@iki.fi>

> 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
> hsivonen@iki.fi
> http://hsivonen.iki.fi/
>
>
>


-- 
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