enable Accessibility, and it should be better. that being said, i haven’t tested Edge. also because of the nature of the project (dealing with Accessibility, etc.) and the load of apps that don’t support it properly, some apps have to be “curated” (usually Electron). if you find an app that doesn’t work, you can send an email/drop an issue on the GitHub repo from the Wooshy’s menu icon. then i’ll investigate and add in the next release. (currently daily alpha.)
SECOND EDIT COZ CANT POST MORE THAN THREE TIMES:
Edge support added to a11 coming later today. but eww. i’m on Ventura that detects stuff install in the background and Edge is installing several stuff without even asking or letting the user decides. eww eww eww. Microsoft doing Microsoft stuff again. the implicit rule is to ask for users at install, and/or let them switch on stuff in the Preferences. eww.
usually web browsers, except Safari, don’t have their Accessibility tree exposed by default, because they’re absolutely slow and greedy with resources when they activate it. there’s some special attributes to be sent to browsers for them to programmatically ask them to expose the tree. no idea if Edge responds to this. i’ll add it to the list of app to investigate for the next release. thanks.
Using Wooshy to reply to this message right now! I wasn’t understanding how it worked (it’s straightforward, but I had to learn that it searches metadata not just text, so it grabs things I wouldn’t think of) until I got a very helpful and quick response from the maker.
yes. Wooshy is pretty straightforward but there’s still some stuff to know. the manual is pretty short. but some things are subject to change, depending on users’ feedback, and my own use. for example, some sort of fuzzy matching will be coming before the beta (if it doesn’t pollute the targets).
also beck, in your specific case with the metadata. the reason why Wooshy is in alpha is because it’s missing an important feature: (all the rest of the engines are there and solid.) there’s gonna be a way to hover on UI elements, and get a popover telling you what are the matching terms that can reach that element. it will be quite useful for the menu bar icons, various other icons in software, webpages, etc. planned of course because Wooshy goes in beta. thanks for reaching out!
Was a long-time user of Shortcat app, then Vimac (no longer being actively developed, I note – now Homerow). The latter works well, but goes the route of overlaying “keywords” across anything that can be activated on-screen, that must then be typed to trigger.
Wooshy’s “live-search” is closer to how I remember Shortcat working. Hope this gets viable!
[EDIT:] Oh wow. Writing this post, had me go look at Shortcat again, which appears to have arisen from the dead! See it has been updated to Apple Silicon, and has some much needed attention given to its homepage.
Downloaded it now as well again – will experiment with both. Fantastic that this space is seeing so much attention, really feel it is an underutilised element of UI control/efficiency, that deserves attention.
down below you have a short video showcasing Wooshy. (you can refresh the page, random videos so you may end up with another one. only three currently.)
you also have a couple of links: YouTube channel showcasing features etc., and the GitHub repo that has the README and where issues are tracked.
thanks. yes, subs are not people’s favorites. but i’m planning to maintain and sustain my apps. for Wooshy, there’s similar alternatives that are one time payment, like Shortcat and Vimac/Homerow. good luck!