W3C home > Mailing lists > Public > public-html@w3.org > April 2010

Re: ISSUE-96 Change Proposal

From: Steven Faulkner <faulkner.steve@gmail.com>
Date: Thu, 1 Apr 2010 16:38:32 +0100
Message-ID: <x2n55687cf81004010838rcc26c2fam6b6e559eec24e5b8@mail.gmail.com>
To: Jonas Sicking <jonas@sicking.cc>
Cc: Shelley Powers <shelley.just@gmail.com>, HTMLWG WG <public-html@w3.org>
hi jonas,
I didn't imply that anything should be removed from HTML5

>I'm curious to hear that you're bringing up programmatic focus.
>Do you mean that
> it's important that the *web page* can programmatically focus a
> particular button in, for example, a date picker? Rather than that the
> user can use accessibility APIs to do this.

I mean that focus needs to be provided natively for all native control
keyboard interactions by the browser .

regards
stevef

On 1 April 2010 16:11, Jonas Sicking <jonas@sicking.cc> wrote:
> On Thu, Apr 1, 2010 at 8:00 AM, Steven Faulkner
> <faulkner.steve@gmail.com> wrote:
>> Hi all,
>> i agree that it is better for  accessibility to have native controls
>> as the properties of these controls can be hooked up to accessibility
>> APIs by the browser.
>> In the case of the new HTML5 controls implemenetd in Opera there are a
>> number of issues:
>> 1. they do not expose any of their properties via an accessibility API.
>> 2. their styles and formatting cannot be modified to suit user requirements.
>> 3. programmatic focus and keyborad operability is limited or non-existent.
>>
>> Until such times that these conditions are met in browsers that
>> implement native HTML5 form controls, then the use of javascript UI
>> libraries that do, provide the above the more accessible choice.
>
> Ah, indeed. It's obvious to me that any and all semantic elements need
> to be appropriately exposed to accessibility APIs. Ranging from <a>
> and <h1> to <input type=date> and <progress>.
>
> It surprises me if Opera does not do this, though it seems to me that
> the proper solution to that problem is to fix the bug in Opera, not
> remove the feature from HTML5.
>
> Likewise with keyboard navigation. See my reply to Shelly in regards
> to styleablility.
>
> I'm curious to hear that you're bringing up programmatic focus. This
> is something I haven't thought or heard about before. Do you mean that
> it's important that the *web page* can programmatically focus a
> particular button in, for example, a date picker? Rather than that the
> user can use accessibility APIs to do this.
>
> If so, why is that important? Could you describe a scenario/use case.
>
> / Jonas
>



-- 
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 Thursday, 1 April 2010 15:39:24 UTC

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