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: Steven Faulkner <faulkner.steve@gmail.com>
Date: Thu, 3 Sep 2009 12:44:22 +0100
Message-ID: <55687cf80909030444h460d1e97rc935e288c06227b9@mail.gmail.com>
To: Henri Sivonen <hsivonen@iki.fi>
Cc: HTMLWG WG <public-html@w3.org>, W3C WAI-XTECH <wai-xtech@w3.org>
hi henri,

the spec states:
WAI-ARIA processing by the user agent *MUST NOT* interfere with the normal
operation of the built-in features of the host language.
If there are no keyboard host language navigation features for say a div
element, but a landmark role added to the div is used for navigation,  how
is the use of ARIA intefering?

 How would you suggest the spec be changed to allow the use of ARIA
landmarks for keyboard navigation?

do you also consider that the use of aria attributes as CSS styling hooks to
be an issue as well?

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

> On Sep 3, 2009, at 14:22, Steven Faulkner wrote:
> how does, for example,  a UA providing keyboard navigation of ARIA
>> landmarks contradict what is stated in Section 7.1[1] in ARIA 1.0?
> Keyboard navigation doesn't usually involve an accessibility API at all. A
> UA typically responds to text input methods without AT / accessibility API
> in between.
> Thus, if keyboardability were sensitive to ARIA when there's no AT
> involved, ARIA would "interfere" with the usual host language features
> beyond accessibility API mapping.
> --
> 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 -
Received on Thursday, 3 September 2009 11:45:11 UTC

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