Right now input type=search, tel, email and url all do not allow any role to be specified. Save for type=search, these are all generally announced as standard 'edit' fields with their accessible names and on-screen keyboards being the primary differentiators between them.
These fields can be given the list attribute to turn them into native comboboxes, but due to the limitations of styling of the native listbox that appears in these cases, authors tend to shy away from them.
I submit that these fields should allow for the combobox role as requiring authors to change the type to text and then having to re-implement entry validation / not getting the benefit of the on screen keyboard modifications seems unnecessary.
Right now
input type=search
,tel
,email
andurl
all do not allow any role to be specified. Save fortype=search
, these are all generally announced as standard 'edit' fields with their accessible names and on-screen keyboards being the primary differentiators between them.These fields can be given the
list
attribute to turn them into native comboboxes, but due to the limitations of styling of the native listbox that appears in these cases, authors tend to shy away from them.I submit that these fields should allow for the
combobox
role as requiring authors to change the type totext
and then having to re-implement entry validation / not getting the benefit of the on screen keyboard modifications seems unnecessary.