Conversation
supportHello, My client (a credit union) is hoping to use your plugin for accessibility compliance for outbound links with keyboard navigation. I’ve run into a few problems in testing: 1) Nothing is focused when opening the modal, so you have to hit tab before “continue” is selected. Once selected, you can hit enter to go to the link (but space bar doesn’t work). 2) If you tab to “cancel”, neither enter nor space bar work to trigger the click. The only way out is with the escape key. 3) Clicking anywhere inside the modal closes the modal. These all seem like simple javascript fixes. Do you think any of this can be updated in a future (soon) release? Thanks! Chad
Thanks for bringing those issues to my attention. I will look at them soon and hopefully get those fixes in.
Excellent! Thank you for the timely response.
Hello, any update on this one?
Hi, checking in again to see if this being addressed.
Still trying to find the time to address this issue that you brought to our attention. This is still planned for the next release, but that could be mid-July at this point with all of the other things on my plate at the moment.
@tincabin just wanted to let you know I havn’t forgotten about your request. I started work on that this afternoon and I expect I’ll have a release out by the end of next week that addresses the issues that you noted.
@tincabin I just pushed the update with the items you noted that needed to be fixed. Thanks again for pointing out those issues.
@jrt341 Thank you so much for following up! My client is in the process of testing a different solution, but I’ll circle back to this with them to see how they want to proceed. Thanks again for looking into the matter. Most such plugins had the same issues with accessibility, so updating definitely puts you over the curve. This reply was modified 5 years, 8 months ago by Tin Cabin Studio .
I ran a quick test and it looks like it’s working as expected for me. Our other solution, not so much. Thanks again for the followup.
Thanks for bringing those issues to my attention. I will look at them soon and hopefully get those fixes in.
Excellent! Thank you for the timely response.
Hello, any update on this one?
Hi, checking in again to see if this being addressed.
Still trying to find the time to address this issue that you brought to our attention. This is still planned for the next release, but that could be mid-July at this point with all of the other things on my plate at the moment.
@tincabin just wanted to let you know I havn’t forgotten about your request. I started work on that this afternoon and I expect I’ll have a release out by the end of next week that addresses the issues that you noted.
@tincabin I just pushed the update with the items you noted that needed to be fixed. Thanks again for pointing out those issues.
@jrt341 Thank you so much for following up! My client is in the process of testing a different solution, but I’ll circle back to this with them to see how they want to proceed. Thanks again for looking into the matter. Most such plugins had the same issues with accessibility, so updating definitely puts you over the curve. This reply was modified 5 years, 8 months ago by Tin Cabin Studio .
I ran a quick test and it looks like it’s working as expected for me. Our other solution, not so much. Thanks again for the followup.