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

(unknown charset) Re: native elements versus scripted

From: (unknown charset) Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
Date: Wed, 7 Apr 2010 15:40:43 +0200
To: (unknown charset) Shelley Powers <shelley.just@gmail.com>
Cc: (unknown charset) Maciej Stachowiak <mjs@apple.com>, HTMLWG WG <public-html@w3.org>
Message-ID: <20100407154043869763.7b3e7c60@xn--mlform-iua.no>
Shelley Powers, Tue, 6 Apr 2010 21:33:12 -0500:
> On Tue, Apr 6, 2010 at 9:09 PM, Maciej Stachowiak <mjs@apple.com> wrote:
  [...]
>> The CSS WG has traditionally shied away from specifying how CSS properties
>> apply to form controls. I think it may be time to revisit that decision.
>> Custom styling of form controls is an important feature, and we will 
>> deliver
>> a real benefit to authors if it works in a consistent way across browsers.
> 
> Is it time, though?
> 
> We have the ability to create custom controls now that are completely
> stylable and without having to introduce potentially dozens or more
> new CSS attributes.

I believe ARIA came about largely because authors were creating their 
own custom controls - even in cases when HTML4 already offers controls? 
Thus, from that angle, native controls will not stop authors from doing 
this. *Unless* it becomes easier to style the native controls. So, 
really, if native controls are meant to have benefits, then ... CSS ...

OTOH, if native controls themselves becomes stylable, then the benefits 
of the native ARIA semantics of these controls disappears, no? And so 
one must use ARIA on the controls, in order to make them accessible ... 
-- 
leif halvard silli
Received on Wednesday, 7 April 2010 13:41:17 UTC

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