https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34113 Owen Leonard <oleonard@myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |29222 Depends on|29222 | Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29222 [Bug 29222] OMNIBUS: Replace the use of jQueryUI -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34113 Jonathan Druart <jonathan.druart+koha@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathan.druart+koha@gmail. | |com --- Comment #1 from Jonathan Druart <jonathan.druart+koha@gmail.com> --- Linking to bug 29222 comment 3 and bug 29222 comment 4, and https://gitlab.com/joubu/Koha/-/commits/bootstrap-autocomplete -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34113 Stephanie Leary <stephanie.leary@equinoxoli.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stephanie.leary@equinoxoli. | |org --- Comment #3 from Stephanie Leary <stephanie.leary@equinoxoli.org> --- The Bootstrap autocomplete components are generally not accessible. In accessibility circles, the Alphagov Autocomplete component (developed for the UK.gov design system) is considered the best. https://alphagov.github.io/accessible-autocomplete/examples/ Adam Silver, who worked on that design system, has a variation on it that supports aliases (see the Demo link at the end): https://adamsilver.io/blog/building-an-accessible-autocomplete-control/ These are the only two autocomplete components I've ever heard screen reader users describe as a good user experience. Both can be styled with Bootstrap classes. -- You are receiving this mail because: You are watching all bug changes.

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34113 --- Comment #5 from David Cook <dcook@prosentient.com.au> --- On a non-Koha project, I just replaced a jQueryUI autocomplete with the Alphagov "accessible-autocomplete", and it went pretty well. The parameters are very similar, and it's pretty easy to style. I like its default styling as well. That said, there is 1 major difference. Instead of binding to an input element, you bind it to a container element and it dynamically creates the input element. Dealing with this difference is probably where most of the work would be, especially for cases where we're using Template::Toolkit to put a value into the "value" attribute for the input. We'll have to do something like put it in a hidden field and then pass it as default value or something using Javascript (which is part of the accessible-autocomplete API). -- The Alphagov folk say that they don't support the autocomplete, but they actively maintain it, and it has current releases. -- You are receiving this mail because: You are watching all bug changes.