Correct link: http://jsbin.com/vegam/1/quiet. On May 9, 2014 11:26 AM, "Daniel Freedman" <[email protected]> wrote:
> It looks like any element with a mousedown handler is treated as a > clickable element in firefox: http://jsbin.com/vegan/1/quiet > > The example only has a div and mousedown handler, no bits of Polymer > anywhere. > > The Polymer gesture library adds mouse listeners so it doesn't have to > wrap addEventListener and keep track of interested elements. However, it > does not add a click event listener, and it seems odd to me that only > Firefox adds the click default action for this strategy. Chrome and IE both > give an accDefaultAction of none. > > Alice, Addy, this seems like a FF bug to me. Can one of you reach out to > their a11y team to figure out why they made this heuristic? > On May 8, 2014 10:46 PM, "Steve Faulkner" <[email protected]> > wrote: > >> >> >> On Thursday, 8 May 2014 23:25:18 UTC+1, Daniel Freedman wrote: >>> >>> 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. >>> >> >> great! thank you. >> >> >> >>> >>> >>> 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/dea3c1f3-3f2a-41c8-b215-fcbc92b7bc59%40googlegroups.com<https://groups.google.com/d/msgid/polymer-dev/dea3c1f3-3f2a-41c8-b215-fcbc92b7bc59%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/CAAUAVAiAyZcqrafcXPkNoHtEDBU1wT_1dVuhopJ5UVyG%2Bu2ppQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
