Re: ISSUE-96 Change Proposal

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.

regards
stevef

On 1 April 2010 15:41, Jonas Sicking <jonas@sicking.cc> wrote:
> On Thu, Apr 1, 2010 at 6:04 AM, Shelley Powers <shelley.just@gmail.com> wrote:
>> In my opinion, this is a bad direction to take across the board.  Do
>> we really want to disregard the strides we've made with JavaScript and
>> CSS and start creating declarative elements? Especially in an
>> environment that is not set up for declarative elements or animations?
>
> My impression is that yes, declarative elements are a good thing. I
> think W3C has been a supporter of declarative markup languages for a
> long time.
>
>> If we're 'allowing' people to come up with their own web designs, why
>> not a progress bar that matches the web site, rather than the
>> operating system? I personally don't want the browser companies and OS
>> to dictate what my page looks like.
>
> Indeed, I think that in order for <meter> and <progress> to be popular
> CSS will need to grow the ability to style them to web authors
> content. Same thing with <input type=date> and some of the other new
> form controls.
>
> We're already seeing this with scrollbars where sites are starting to
> create much less accessible pages in order to hack together their own
> scrollbars using piles of <divs> in order to get them to look the way
> they want. I believe Apple has stepped up and proposed some extensions
> to CSS to help with this situation.
>
> My point is that this isn't something that HTML should fix, but
> something that needs to be fixed using CSS expansions.
>
> / 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:02:06 UTC