WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: How useful is the datalist element?


From: Jeremy Echols
Date: May 26, 2017 4:43PM

This is very disappointing to hear. Thanks for the response.

I don't know enough about the accessibility APIs to know what kind of bug to file. I'm assuming the browser is sending the wrong information or too much information or something, but is there some way to see exactly what NVDA is being told by the browser? And I'm not sure what the expected behavior would even be. It seems that the concept of a "combo box" hasn't been filled in yet by the w3c "aria practices" authors: https://github.com/w3c/aria-practices/issues/31.

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Chaals is Charles McCathie Nevile
Sent: Friday, May 26, 2017 3:32 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] How useful is the datalist element?

Interesting question - coincidentally, today someone proposed a different improvement by allowing grouping:

My sense is that implementation is still immature. And not very good.
File bugs on browsers...


On 27/05/17 00:20, Jeremy Echols wrote:
> It seems like being native HTML, it would be pretty accessible, but in my testing with Firefox and NVDA, it seems like it's... just painful to use. For instance, NVDA doesn't notify me when typeahead options show up, but worse, when I use the down-arrow to start selecting items, it re-reads the input label and aria-describedby text... on every single down-arrow selection.
> Are there JavaScript typeaheads which are better? Is support for datalist just at such a bad point that it shouldn't be used?
> > > archives at http://webaim.org/discussion/archives
> --
Charles McCathie Nevile - standards - Yandex
<EMAIL REMOVED> - Find more at http://yandex.com