Re: [orca-list] Odd issue with the Riot web client

[Joanmarie Diggs <jdiggs igalia com>]

Good to know. Thanks!

If you are able to get a later version of chrome/chromium you'll get 
other bug fixes. And while we talk about "chromium", Orca's support 
should kick in for Chrome. 
https://www.google.com/chrome/dev/?platform=linux right now is at 
version Version 80.0.3964.0. My locally-built-by-me chromium from a few 
days ago, is at version 80.0.3966.0.

Just in case you're curious (Joanie says, trying to suck Nolan into the 
early-tester cabal) <grins>


On 11/13/19 6:52 PM, Nolan Darilek wrote:
> FWIW, I finally installed Chromium, and this doesn't happen with 
> Chromium 77.0.3865.120 Fedora Project and Orca master. So seems specific 
> to Firefox.
>
>
> On 11/5/19 3:05 PM, Joanmarie Diggs wrote:
> > I can reproduce this. It looks like an Orca bug. I'm still debugging 
> > it, but will hopefully have it fixed before too long. I don't think 
> > it's a regression though. Or if it is, it's super old. I went back to 
> > Orca 3.30 and the problem happens there....
> >
> > On 11/1/19 11:29 AM, Nolan Darilek wrote:
> > > Hey folks,
> > >
> > >
> > > The Riot developers have been pouring lots of effort recently into 
> > > making their web-based Matrix client accessible. But I'm experiencing 
> > > a pretty significant issue with their new text entry system for 
> > > messages that they can't duplicate under NVDA. I'm wondering if any 
> > > Orca users are seeing the same, and if this can be diagnosed as 
> > > either a Firefox/Orca issue under Linux, or as something they aren't 
> > > doing correctly on their end. To test, you'll need a Matrix account. 
> > > Once you have one and are logged in, visit this instance with 
> > > accessibility improvements:
> > >
> > >
> > > https://riots.im/adhoc/a11y
> > >
> > >
> > > Join a room or chat. You'll probably be automatically focused into 
> > > the message input field and put in focus mode. Once there, enter 
> > > browse mode and try arrowing up.
> > >
> > >
> > > Apparently, NVDA handles this use case fine both in the accessibility 
> > > build and the development build at riot.im/develop. Orca, on the 
> > > other hand, won't let me arrow up. I hear "Newline," followed by some 
> > > buttons, and focus lands back in the message entry field. The only 
> > > way to escape this field is to enter browse mode and use b/B/h/some 
> > > other quick navigation key, then hope you don't land back in the mud. 
> > > Happens under Orca master as of a few minutes ago and Firefox nightly 
> > > as of a few days ago, but it's happened for a bit now so I don't 
> > > think it's a bleeding-edge regression. Apologies for not reporting 
> > > it--been a bit busy and it hasn't been high enough priority for me.
> > >
> > >
> > > Is there any actionable feedback I can give the Riot folks to fix 
> > > this? They're pretty actively looking for feedback in the 
> > > #a11y:matrix.org room, so if you're Matrix-inclined and want to give 
> > > it then there is the best place, or I'll happily relay it otherwise.
> > >
> > >
> > > Thanks a bunch.
> > >
> > > _______________________________________________
> > > 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