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

[Nolan Darilek <nolan thewordnerd info>]

Sorry for the spam, but I just discovered another interesting detail 
that might help diagnose this:


If I type anything into the field, then enter browse mode, I can arrow 
up just fine. But if the field is empty, arrowing up (not down) traps me 
in it. The field also says "Opens list box" when empty, but not when 
there is any content.


I'm wondering if this input is classified as a list widget of some kind, 
and maybe eats up-arrows even if in browse mode? That would be 
consistent with a widget like this which, presumably, lets me arrow up 
to previous messages I sent and edit them.


Anyhow, still not sure where the specific issue lies, but hopefully I've 
given enough of a pointer.





On 11/1/19 10: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