Why did the accessibility features are dropped in the recent version (1.5.x) of Dropkick?

[vraa]

Recently I'm tasked with making the 'fancy' select boxes accessible in my project. It's legacy code base, split into multiple tiny projects. In one projects, they were using Drop kick version 1.3.x and in another it was 1.5.x. Surprisingly, the older version (1.3.x) is very accessible and JAWS / screen readers didn't have problem reading the content in Dropkick.

But in latest version, I see the accessibility feature is explicitly turned off using aria-hidden=true.

Is there any specific reason to do that? Would be interested to know.

thanks.

[Robdel12]

I'm pretty sure 1.x was never accessible. I can't remember why or when the aria-hidden=truewas added either. I might be able to check it out. All of my time is dedicated to getting 2.0 out the door to replace 1.x.

If you can check out 2.0. It's fully accessible. And MUCH better.

[vraa]

@Robdel12 Thanks, I can see that the version 2 has many accessibility stuff baked in. For 1.5, I had to write code to override the DOM created by Dropkick to add aria features. Once 2.0 is out, will upgrade to it.

As feature request, it will be great if you could provide external hooks / or send us event so that we can run custom JavaScript code. For example, in order to add aria attributes, I had to run my custom function after certain milliseconds through setTimeout to let Dropkick do its work. But if Dropkick had provided an event mechanism, say, 'dropkick:done', I would have simply listened to that event and ran my custom code after Dropkick had done. The code will be much more clean and readable.

Thanks for your effort in developing Dropkick. 👍

[Robdel12]

Check out the API 2.0 offers. I think it should cover that :)