E-mail List Archives
Thread: Complex UI being baked into browsers.
Number of posts in this thread: 3 (In chronological order)
From: Sean Murphy
Date: Thu, Oct 18 2018 4:39AM
Subject: Complex UI being baked into browsers.
No previous message | Next message →
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
From: Swift, Daniel P.
Date: Thu, Oct 18 2018 6:40AM
Subject: Re: Complex UI being baked into browsers.
← Previous message | Next message →
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 ADDRESS REMOVED = ] On Behalf Of Sean Murphy
Sent: Thursday, October 18, 2018 6:40 AM
To: = EMAIL ADDRESS 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
From: Brandon Keith Biggs
Date: Fri, Oct 19 2018 4:52AM
Subject: Re: Complex UI being baked into browsers.
← Previous message | No next message
Hello,
Who designs these widgets? The date picker doesn't seem like a very
customizable widget. Neither does datalist.
I just looked at the date picker on Firefox and it looks great to me as a
screen reader user. It took me 30 seconds to figure out exactly how it
worked. The problem is that I would like to know days, like if it is
Tuesday or Friday.
Are sighted users able to select from a calendar rather than move through
numbers?
Creating these types of HTML widgets by default is exactly what needs to
happen. It seems as if Javascript has an extremely fast implementation
curve in Browsers, but HTML widgets not so much. Why? It's like making tons
of different frostings on the cake while not changing the cake very fast.
Now we have frosting that is pretending to be cake!
Aria also is extremely advanced compared to normal HTML widgets.
I think Web Components:
https://developer.mozilla.org/en-US/docs/Web/Web_Components
are supposed to be kind of a beginning in solving this problem, but the few
components I've seen at:
https://www.webcomponents.org/
I would rate pretty close to 0 for screen reader and keyboard accessibility.
It looks like the Web Platform Working Group:
https://www.w3.org/WebPlatform/WG/
Are the ones in charge of HTML.
I'm not sure where a good discussion place for this would be.
If anyone knows, I would love to join!
Thank you,
Brandon Keith Biggs <http://brandonkeithbiggs.com/>;
On Thu, Oct 18, 2018 at 5:40 AM Swift, Daniel P. < = EMAIL ADDRESS REMOVED = > wrote:
> 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 ADDRESS REMOVED = ] On
> Behalf Of Sean Murphy
> Sent: Thursday, October 18, 2018 6:40 AM
> To: = EMAIL ADDRESS 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
> > > at http://webaim.org/discussion/archives
> > > > > >