Re: Valuenow not defined for input type controls?

Sorry, I didn't explain that very well nor did I ask the right question. 

When I create a combobox using an element other than an input field, I 
need some way to set the value of that combobox.  In Dojo we have been 
using the ARIA valuenow property since the element that we assign the role 
of combobox may not have an HTML value property.  But, ARIA does not 
define a valuenow property for combobox.  There needs to be some way to 
set the value on a combobox so I think a valuenow or value property should 
be defined for all of the form-type roles.

The current Role specification lists the definition for the abstract input 
role as, "Generic type for widgets that can have a value."   However, 
there is no property defined for "value" is it implicitly assumed? 


Becky Gibson
Web Accessibility Architect
IBM Emerging Internet Technologies
5 Technology Park Drive
Westford, MA 01886
Voice: 978 399-6101; t/l 333-6101
blog: WebA11y

"Charles McCathieNevile" <> wrote on 01/08/2008 09:45:27 

> On Tue, 08 Jan 2008 14:17:24 +0100, Becky Gibson 
> <> wrote:
> >
> > The Dojo toolkit currently uses the valuenow property on items which 
> > have a value attribute which can change such as combobox and
> > filteringSelect. But, as I look at the ARIA spec, the valuenow 
> > is not
> > defined on some roles which have an HTML value attribute.
> > Should we instead just be updating the HTML value
> IMHO, yes. Allowing ARIA attributes on things that need them is one 
> but adding them as a redundant possibility to replace things that 
> exist just introduces confusion IMHO...
> cheers
> Chaals
> -- 
> Charles McCathieNevile  Opera Software, Standards Group
>      je parle franšais -- hablo espa˝ol -- jeg lŠrer norsk
>   Try Opera 9.5:

Received on Tuesday, 8 January 2008 16:03:09 UTC