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: Henri Sivonen <hsivonen@iki.fi>
Date: Thu, 3 Sep 2009 14:28:29 +0300
Cc: HTMLWG WG <public-html@w3.org>, W3C WAI-XTECH <wai-xtech@w3.org>
Message-Id: <D40F2B35-12A1-4433-AFD9-7093A7F4183B@iki.fi>
To: Steven Faulkner <faulkner.steve@gmail.com>
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/
Received on Thursday, 3 September 2009 11:29:15 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:07 UTC