WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Complex UI being baked into browsers.

for

From: Swift, Daniel P.
Date: Oct 18, 2018 6:40AM

Sean:

See the link below regarding the process of an 'idea' moving towards a W3C Recommendation:
https://www.w3.org/2018/Process-20180201/#Intro

In my experience/opinion, the biggest hurdle isn't the ideas becoming recommendations so much as browser adoption. Look at the input type date for instance ... the 'can I use' site shows that the input type date still isn't fully supported by major browsers (I'm looking at you iOS Safari and Firefox):
https://caniuse.com/#searchÚte

Yet - according to the timestamp on this post at Stack Overflow (below), this input type has been available for over 5 years.
https://stackoverflow.com/questions/7372038/is-there-any-way-to-change-input-type-date-format

If such initiatives exist, browser implementation is going to take awhile.

Dan Swift
Senior Web Specialist
Enterprise Services
West Chester University
610.738.0589

-----Original Message-----
From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf Of Sean Murphy
Sent: Thursday, October 18, 2018 6:40 AM
To: <EMAIL REMOVED>
Subject: [WebAIM] Complex UI being baked into browsers.

All,

I am wondering if there is any initiatives or work being done to bake in complex UI's like combo boxes, menus, pop-up menus, tree views, ETC? Simular to what is available with the native HTML button element. I see this as a major win to accessibility if it is correctly done. the element must be able to provide the same customization for visual efects which you can apply now. I just see this removing a lot of heavy lifting and duplication of work by the developers.

Thoughts?

Sean

My experience is the part