Comment 11 for bug 1187993

I smell what you're cooking, Jason. Just to be clear, if we introduce a new JS framework to the catalog, it should (must, IMO) coincide with removing Dojo. Since autosuggest was the reason Dojo was reintroduced to the catalog, replacing Dojo as we replace autosuggest is a natural fit. (All of the other Dojo code in the catalog, IIRC, is limited to things like dojo.byId(), etc., stuff that's easy to replace).

Regarding JQuery, Angular uses a subset of jquery internally. On page load, it checks for the presence of jquery proper and if it's not found, it activates its own jquery shim code. Blending the two together is not unheard of. Based on what I've seen in the wild, I'd say that combining them is what most people do. I have avoided loading jquery so far in the staff client code, relying instead on the angular shim, because jquery seemed unnecessary. If it serves a larger purpose (e.g. autosuggest), maybe it's warranted. *long shrug*. Of course, new dependencies mean additional version maintenance, etc., etc.

With a cursory search, I'm finding lots of Angular typeahead plugins and tutorials, but the only ones that address accessibility specifically that I've found use JQuery / Angular+Jquery. (Speaking of, here's a worthy read: https://webaccessibility.withgoogle.com/unit?unit=6&lesson=13). I'm still digging...