Accessibility...

[patrickhlauke]

Google has expertise in-house to create functional, beautiful, web-component stuff that is also accessible. It would be great if high-profile demos like these would actually take advantage of those resources to create things that work not just for sighted mouse/touchscreen users...

[ebidel]

I agree there's a lot that can be done. The demo is meant to be primarily mobile first, but could use a lot of keyboard love for desktop.

[ragingwind]

@ebidel Sorry it's beside the point little. All of poly-example is to primarily mobile first? is this rule refer to Polymer?

[ebidel]

Everything should be mobile first :) polymer or not.

I didn't spend much time on the desktop view. On Nov 21, 2014 5:00 PM, "Jimmy Moon" notifications@github.com wrote:

@ebidel https://github.com/ebidel Sorry it's beside the point little. All of poly-example is to primarily mobile first? is this rule refer to Polymer?

— Reply to this email directly or view it on GitHub https://github.com/ebidel/polymer-gmail/issues/2#issuecomment-64051552.

[ragingwind]

Yeah you're right. I think so too. I just wonder that :)

[patrickhlauke]

This is not purely about keyboard access. Even on mobile, there are other aspects here such as having components actually convey their role (instead of just being generic collections of <span>s hidden under a shadow-dom carpet). See "Do your custom elements provide semantic information?" for instance https://www.polymer-project.org/articles/accessible-web-components.html /cc @addyosmani

[ebidel]

Like I said before, there's plenty that can be done in the convenience of unlimited time and resources. If you'd like to help, please submit a PR. On Nov 21, 2014 5:42 PM, "Patrick H. Lauke" notifications@github.com wrote:

This is not purely about keyboard access. Even on mobile, there are other aspects here such as having components actually convey their role (instead of just being generic collections of s hidden under a shadow-dom carpet). See "Do your custom elements provide semantic information?" for instance https://www.polymer-project.org/articles/accessible-web-components.html /cc @addyosmani https://github.com/addyosmani

— Reply to this email directly or view it on GitHub https://github.com/ebidel/polymer-gmail/issues/2#issuecomment-64055655.

[patrickhlauke]

My resources are currently a bit more stretched than Google's...but I'll put it on my to-do list ;)

[marcysutton]

I think this could really use some taco buttons. http://marcysutton.github.io/accessibility-of-web-components/slides.html#/slide18

[JGSolutions]

Polymer is an interest for me. Haven't done any polymer development yet but will in the near future. Of course this project is a good starting point. I tested this example on my samsung 3 mini and everything is slow. From scroll events to touch events. I guess more performance development is needed?

[rizvan]

Must say a best start , would love to work with you on this project . Will learn new things and implement .