E-mail List Archives
Re: Does role="combobox" eat the identity of nested elements?
From: Birkir R. Gunnarsson
Date: Sep 7, 2019 11:10AM
- Next message: Don Raikes: "Re: JAWS/IE 11 not announcing aria-live regions?"
- Previous message: Greg Jellin: "JAWS/IE 11 not announcing aria-live regions?"
- Next message in Thread: glen walker: "Re: Does role="combobox" eat the identity of nested elements?"
- Previous message in Thread: Steve Green: "Re: Does role="combobox" eat the identity of nested elements?"
- View all messages in this Thread
You're right, the combobox role overrides the role of the text input field.
You should be able to find it using "c" in Jaws/NVDA (just like you
would find a <select>). You should also be able to find it with the
arrow keys in browse mode.
If you can't, that's a bug I think.
The combobox role triggers application/forms mode so once inside the
combobox screen reader browse commands / keyboard navigation stop
working and all navigation within the widget is the responsibility of
the widget author.
If you put other widgets inside the combobox you must control
navigation with Javascript.
I agree with Steve that comboboxes are unnecessarily complex and the
functionality can be implemented differently, either with a <select>
or listbox if it's just a drop down function, or a com bination of
live regions and arrow key navigation for inline autocomplete search,
use the value attribute of the search input to indicate currently
selected option from suggestions.
If you are tackling a specific problem I can probably find some
examples of solutions I'd recommend.
On 9/7/19, Steve Green < <EMAIL REMOVED> > wrote:
> If you are referring to the examples at
> https://www.w3.org/TR/wai-aria-practices-1.1/#combobox, my advice is not to
> use any of them. They might be compliant in theory, but they give a truly
> horrible and incomprehensible user experience. Using JAWS 2019, the
> behaviour is different in each browser, but it's bad in all of them. It
> would take hours to describe all the issues, so I suggest people just try it
> for themselves.
>
> Part of the problem is that the design patterns are trying to be too clever.
> They all include autocomplete, but most authors don't want that - they just
> want to replicate the exact behaviour of a native combobox. None of the
> design patterns does this, and there is no point adding extra features such
> as autocomplete or grid popups until they do. Is this too much to ask for?
>
> Steve Green
> Managing Director
> Test Partners Ltd
>
>
>
- Next message: Don Raikes: "Re: JAWS/IE 11 not announcing aria-live regions?"
- Previous message: Greg Jellin: "JAWS/IE 11 not announcing aria-live regions?"
- Next message in Thread: glen walker: "Re: Does role="combobox" eat the identity of nested elements?"
- Previous message in Thread: Steve Green: "Re: Does role="combobox" eat the identity of nested elements?"
- View all messages in this Thread