Hi Steve, Alice and Addy alerted me to this the other day, and I'm going to carve out some time to work on this, probably tomorrow.
On Thu, May 8, 2014 at 3:16 PM, Steve Faulkner <[email protected]>wrote: > I have found that on non interactive polymer based custom elements, when > using Firefox, a click handler is exposed via accessibility APIs. This > causes assistive technology such as a screen reader to announce the custom > element as clickable (when it isn't). > > Would appreciate some help tracking down the cause, as it is annoying to > users <https://twitter.com/MarcoInEnglish/status/464383799640735745>. > > custom element example where the issue occurs: > https://github.com/ThePacielloGroup/w3c-heading demo page > http://thepaciellogroup.github.io/w3c-heading/ > > > > > Follow Polymer on Google+: plus.google.com/107187849809354688692 > --- > You received this message because you are subscribed to the Google Groups > "Polymer" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/polymer-dev/d32ad8ac-6a0d-41aa-baeb-492d04e7ed87%40googlegroups.com<https://groups.google.com/d/msgid/polymer-dev/d32ad8ac-6a0d-41aa-baeb-492d04e7ed87%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/CAAUAVAhdu3qbDbeF5ZRWvue5fpJTFGqDG_3CeJ6MQA%3D0GFA%3DhA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
