Re: Questions arising from ARIA/HTML5 integration

hi smylers,

In pre-HTML-5 browsers they are simply a textbox.

yes I understood this.


In HTML 5 browsers the browser can choose any UI they want; the spec
only defines the values which the form elements have.  So a colour
picker could be a button with a coloured square on it, where clicking
that square brings up the platform's generic colour-picker dialog box.
There might not be a textbox-like part of it anywhere.

so whatever the control that is presented it should be mapped to the
accessibility APIs as appropriate, if its a button that opens a colour
picker then its should be expsoed as a button with an accessible name value
of color picker or whatever.

regards
stevef

2009/9/1 Smylers <Smylers@stripey.com>

> Steven Faulkner writes:
>
> > <input type=date>
> >  <input type=time>
> >  <input type=datetime>
> >  <input type=datetime-local>
> >  <input type=month>
> >  <input type=week>
> >  <input type=color>
> >  <input type=file>
> >
> > these all appear as text boxes with a button/keystroke associated to open
> a
> > dialog no?
>
> Not necessarily.
>
> In pre-HTML-5 browsers they are simply a textbox.
>
> In HTML 5 browsers the browser can choose any UI they want; the spec
> only defines the values which the form elements have.  So a colour
> picker could be a button with a coloured square on it, where clicking
> that square brings up the platform's generic colour-picker dialog box.
> There might not be a textbox-like part of it anywhere.
>
> Smylers
>



-- 
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