RE: Auto and edit combo box status of ARIA pattern

Matt's been doing a lot of work to make a design pattern example that matches the ARIA 1.1 specification, however this is not safe to use within production environments by developers because the support within browsers and assistive technologies has a long way to go before it will work accessibly for public usage.

We spoke of this last week at TPAC, and as a result of these concerns the following issue was raised:
https://github.com/w3c/aria-practices/issues/529
Which addresses the issue that developers are likely to want to use unsafe widgets in production development environments, which as the potential to cause major if not critical accessibility issues for general users in some cases if accompanying testing is not performed at the same time.

At present, the following blog page explains the only safe way at present to implement editable ARIA Combobox widgets within production environments, which is to adhere strictly to the ARIA 1.0 design pattern until support becomes available by browsers and ATs for the newer design pattern.
https://www.levelaccess.com/differences-aria-1-0-1-1-changes-rolecombobox/



Bryan Garaventa
Accessibility Fellow
Level Access, Inc.
Bryan.Garaventa@LevelAccess.com
415.624.2709 (o)
www.LevelAccess.com

From: Sean Murphy (seanmmur) [mailto:seanmmur@cisco.com]
Sent: Wednesday, November 22, 2017 4:56 PM
To: w3c-wai-ig@w3.org
Subject: Auto and edit combo box status of ARIA pattern

I am just wondering what the status of the ARIA pattern for Auto/Edit combo boxes is currently?

Question, shouldn't this be a default wegit of a browser simular to select, edit, radio button, ETC. AS I would have thought it would save a lot of work for the devs. There are a couple of other wigets which I feel should be a default element of a browser as well.

Regards,
Sean