Re: [orca-list] Chrome and --force-renderer-accessibility flag



Do you know how long this might take? I am working on an app that requires Chrome to be accessible out of the box.

 

 

Sent from Mail for Windows 10

 

From: Joanmarie Diggs
Sent: Saturday, July 18, 2020 7:58 AM
To: Andy Borka; orca-list gnome org
Subject: Re: [orca-list] Chrome and --force-renderer-accessibility flag

 

A new commit landed last week which should again make --force-renderer-

accessibility unnecessary. But it's a more conservative solution and

will need lots of testing. You should see it in version 86 once that

hits the dev channel.

 

--joanie

 

On Fri, 2020-07-17 at 21:38 -0400, Andy Borka via orca-list wrote:

> Hi,

> IIs there any new news about the force renderer accessibility flag in

> Chrome? Last I checked, Chrome 85 had reverted to manual activation

> instead of automatic.

> Sent from Mail for Windows 10

> _______________________________________________

> 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]