ChromeVox is a Chrome screen reader extension by Google. http://www.chromevox.com/ William and Chris mentioned in IRC that it would be nice for visually impaired users to have a way to install ChromeVox without having to visit the Chrome Store. I found these instructions for auto-installing extensions: https://developer.chrome.com/extensions/external_extensions.html Using the instructions, I created this JSON file which will cause ChromeVox to be installed when you launch Chromium. It just needs to be placed in /usr/lib/chromium/extensions. http://dev.gentoo.org/~floppym/chromium/kgejglhpjiefppelpmljglcjbhoiplfn.json We just need to figure out a good way of deploying this JSON file. A few choices: 1. Create an ebuild for it. 2. Add a use flag for www-client/chromium and install it from there. 3. Have chromium install a bash script to create the JSON file at runtime. Personally, I prefer the first option. Any further thoughts, comments, objections?
Yes, I think the ebuild would be the best option, under app-accessibility. If you want I'll write one. We would just put the json in ${FILESDIR} and install it.
I'd vote for the global accessibility use flag, but I do think that the ebuild is viable.
Thinking this over, if the chromium and chrome ebuilds use the global accessibility use flag to install this json file, that would be the most automatic way to do this, so that is what I support now as well.
For a separate ebuild, there is no need to put it in files/ the one line can be echo'd into the file direct from the ebuild. Same for a use flag trigger in chromium. It'll save another inode ;) My favorites are in order: USE flag in chromium ebuild installer script (python or bash) (could be easily expanded to install a choice of any popular extensions available) Then the user can install them if/when they want. rebuilds, not necessary.
A USE flag (accessibility) on the chromium and google-chrome ebuilds works for me. phajdan.jr: Do you have any suggestions/objections?
(In reply to Mike Gilbert from comment #5) > A USE flag (accessibility) on the chromium and google-chrome ebuilds works > for me. > > phajdan.jr: Do you have any suggestions/objections? Sounds good to me.
I'm not sure how feasible this is. At some point since the last update the extension got merged into the main Chromium source tree (References easily as far back as 69.x.y.z). It appears to be linked to both building with `nacl` and the `chromeos` target[1]. I'm not sure what _else_ this enables, but we explicitly disable `nacl` in the build due to an old bug[2]. What I imagine the steps forward look like: a. Find out if nacl still works. (pnacl was removed in 2022; our comment is probably obselete?) b. patch the build to enable ChromeVox as a feature independent of ChromeOS builds c. test d. ??? e. PROFIT! I'm willing to see what we can do to make this available but don't really have the time at the moment. Patches welcome! 1: https://github.com/chromium/chromium/blob/main/docs/accessibility/os/chromevox_on_desktop_linux.md 2: https://bugs.chromium.org/p/chromium/issues/detail?id=269560
