Bug 34113

Summary:	Replace the use of jQueryUI autocomplete
Product:	Koha	Reporter:	Owen Leonard <oleonard>
Component:	Templates	Assignee:	Owen Leonard <oleonard>
Status:	NEW ---	QA Contact:	Testopia <testopia>
Severity:	enhancement
Priority:	P5 - low	CC:	jonathan.druart, stephanie.leary, testopia
Version:	Main
Hardware:	All
OS:	All
Change sponsored?:	---	Patch complexity:	---
Documentation contact:		Documentation submission:
Text to go in the release notes:		Version(s) released in:
Circulation function:
Bug Depends on:
Bug Blocks:	29222

Description Owen Leonard 2023-06-23 14:36:06 UTC

As discussed in Bug 29222, jQueryUI autocomplete should be replaced. The last time I checked it was used in these places:

  - Checkout and patron header searches
  - Article request patron search
  - Course reserve instructor search
  - Holds patron search
  - UNIMARC 210c plugin
  - UNIMARC 225a plugin

Possible replacement candidate: https://tarekraafat.github.io/autoComplete.js/.

Comment 1 Jonathan Druart 2023-07-04 15:09:05 UTC

Linking to bug 29222 comment 3 and bug 29222 comment 4, and https://gitlab.com/joubu/Koha/-/commits/bootstrap-autocomplete

Comment 2 Jonathan Druart 2023-07-05 06:51:32 UTC

There is also https://iqbalfn.github.io/bootstrap-autocomplete/

Comment 3 Stephanie Leary 2024-08-11 17:53:36 UTC

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.