If they allow --force-renderer-accessibility, or if it won't be required, then the only thing that suffices is probably the fact that chromium engine used would be new enough... That is why it works for electron apps/etc if electron is new enough, for example. vscode, probably other things W dniu 28.11.2019 o 15:39, Jace Kattalakis via orca-list pisze:
Adding to this, for me exporting the variable worked in Ubuntu LTS then adding the flags to the launcher. So, Joany's on vacation so this isn't aimed at her (but enjoy your vacation Joany and a happy turkey day), but once it's in the stable version, theoretically would I not need those flags and variable set or...? Also, should I get in touch with other Chromium-based browsers to see about adding the Orca support in them or...? On 28/11/2019 13:31, Didier Spaier wrote:Hello, Joanie wrote it here: https://wiki.gnome.org/Projects/Orca/Chromium Best regards, Didier Le 28/11/19 à 14:25, Vojtěch Šmiro via orca-list a écrit :Hello. How to set Google chrome accessibility to 1? Someone wrote here, it must be set from 0 to 1 in some file. Thanks a lot. Best regards Vojta._______________________________________________ orca-list mailing list orca-list gnome org https://mail.gnome.org/mailman/listinfo/orca-list Orca wiki: https://wiki.gnome.org/Projects/Orca Orca documentation: https://help.gnome.org/users/orca/stable/ GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html_______________________________________________ orca-list mailing list orca-list gnome org https://mail.gnome.org/mailman/listinfo/orca-list Orca wiki: https://wiki.gnome.org/Projects/Orca Orca documentation: https://help.gnome.org/users/orca/stable/ GNOME Universal Access guide: https://help.gnome.org/users/gnome-help/stable/a11y.html
Attachment:
signature.asc
Description: OpenPGP digital signature