We are liking many features of the Web Widget, but a few things about its implementation are making it hard for us to perform some tasks we are really hesitant to compromise on:
1. Accessibility: we would like our users who rely on the keyboard only to be able to launch the Web Widget by some means other than clicking / tapping on the #launcher button. There may be a few ways to enable this, but having the Widget launcher as a button / focusable DOM element (in our page's DOM -- much the way the Feedback Tab is) would be one simple way to do so;
2. We would like to track (using, e.g., custom events in Google Analytics) when our users click on the Web Widget seeking help. With the iframe #launcher, any clicks on child elements among the widget's contents do not register in our window context, so the only way we have to detect click events on the tab is to place a transparent overlay on top of the Widget and trigger `zE.activate` (we then remove the overlay, so that it will not cover the buttons of the contact form)
If you would be open to exploring some solution in a future iteration of the Widget, or should you have any suggestions as for how we might achieve the accessibility and tracking ends here, please advise. Thank you!
댓글을 남기려면 로그인하세요.