Re: [orca-list] Using force-renderer-accessibility flag



If you change .profile .bashrc or .bash_aliases it's a good idea to source
.profile or source .bashrc or source .bash_aliases to get the effect of
the change you just made.  That change will also be in effect on next
reboot.


On Thu, 30 Dec 2021, Vojtech ?miro via orca-list wrote:

Hello,

I wrote it in .Profile. But may it have in .bashrc or in other files?

Thanks a lot.

Best regards

Vojta.

Dne 29. 12. 21 v 13:27 Vsevolod Popov via orca-list napsal(a):
Hello Didier and everyone,

29.12.2021 14:51, Didier Spaier via orca-list ?????:
for a recent Chrome you just need:
ACCESSIBILITY_ENABLED=1

Thank you, it helped! I didn't know about this flag existance.
I put this parameter to ~/.pam_environment.
And now everything works! Thank you again for all help!

-
regards,
Vsevolod
https://github.com/sevapopov2/
_______________________________________________
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




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]