Re: [orca-list] Chrome unstable and force-renderer-accessible

["Tyna Pelletier-Bilodeau" <ecole tyna gmail com>]

It is definitely still required. The experiment I made was to see if even with 
it not passed to chromium it would crash, which would have pointed the blame 
onto another part than the accessibility stack. However since it did not crash, 
and crashed again as soon as I enabled the accessibility stack... It is 
definitely problematic there.

On Mon Jun 22, 2020 at 6:14 AM CEST, Janina Sajka via orca-list wrote:
> Joanie posted here a few weeks ago about that flag being again required
> until further notice. I've not seen any further notice that iit is again
> not required. Did I miss that?
>
>
> Her message is here:
> https://mail.gnome.org/archives/orca-list/2020-May/msg00298.html
>
> Best,
>
> Janina
>
> Orca screen reader developers writes:
> > Right, but that wasn't the question. The original problem wanted to know why
> > Chrome unstable 83 in Mate worked without the flag, but now Chrome unstable
> > 85 does require it.
> >
> >  
> >
> > From: orca-list <orca-list-bounces gnome org> On Behalf Of Nolan Darilek
> > Sent: Sunday, June 21, 2020 10:00 AM
> > To: orca-list gnome org
> > Subject: Re: [orca-list] Chrome unstable and force-renderer-accessible
> >
> >  
> >
> > You spelled the argument wrong. --force-renderer-accessibility
> >
> >  
> >
> > On 6/21/20 12:46 PM, sonfire11--- via orca-list wrote:
> >
> > Hi,
> >
> >  
> >
> > Some time ago, I used Chrome unstable 83.0 in Ubuntu 20.04. Everything
> > worked except for a focus problem on initial Chrome startup. Yesterday, I
> > updated Chrome unstable to 85.x. Now, everything is broken. Chrome unstable
> > 85 requires force-renderer-accessible when it didn't before, and it appears
> > that setting ACCESSIBILITY_ENABLED=1 makes no difference. Can anyone confirm
> > this problem, or advise on what to do from here? I use Ubuntu 20.04 with
> > Orca master and Mate 1.24.
> >
> >  
> >
> >
> >
> >
> >
> > _______________________________________________
> > orca-list mailing list
> > orca-list gnome org <mailto: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
>
>
> --
>
> Janina Sajka
>
> Linux Foundation Fellow
> Executive Chair, Accessibility Workgroup: http://a11y.org
>
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Chair, Accessible Platform Architectures http://www.w3.org/wai/apa
>
> _______________________________________________
> 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