1489695 - [Ubuntu] Built-In Screenreader tool for Ubuntu does not read doorhanger information

Status: RESOLVED INVALID

(Firefox :: Disability Access, defect, P3)

Description

[u554753]

Ubuntu 18.04 x64
Version 62.0
Build ID: 20100830143136
Mozilla/5.0 (X11; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0

Steps to Reproduce:
1. Go to Settings in Ubuntu 
2. Turn "Screen Reader" On
3. Open Firefox
4. Navigate to a website that involves a doorhanger to appear.
5. Focus on the doorhanger

Expected Result:
Ubuntu screenreader reads the doorhanger information.

Actual Result:
Nothing is read to the user.

Comment 1

[Marco Zehe (:MarcoZ)]

Joanie, ever heard reports of this from users? Anything special with Orca and doorhangers?

Comment 2

[Joanmarie Diggs]

I thought we had this fixed. I'll look into it. Thanks for the ping.

Comment 3

[Joanmarie Diggs]

Grover, to save me (Orca developer) some time, could you please provide a link to a site which reliably fails for you?

Comment 4

[u554753]

So I'm starting to wonder if this might be related to running Ubuntu in a Virtual Machine as I reported this bug when assisting with testing another feature. The screenreader reads normal Ubuntu programs but not anything in Firefox. Are there specific settings or shortcuts I need to do to be able to use the built-in screenreader in a Virtual Machine?

Comment 5

[Alex ARNAUD]

(In reply to Grover Wimberly IV [:Grover-QA] from comment #4)
> So I'm starting to wonder if this might be related to running Ubuntu in a
> Virtual Machine as I reported this bug when assisting with testing another
> feature. The screenreader reads normal Ubuntu programs but not anything in
> Firefox. Are there specific settings or shortcuts I need to do to be able to
> use the built-in screenreader in a Virtual Machine?

Not really. The only thing you should know is to launch Orca before to start Firefox to ensure Firefox is correctly connected to AT-SPI (accessibility bus). It seems Firefox doesn't enable accessibility if no assistive technology is connected to it.

Best regards,
Alex.

Comment 6

[Joanmarie Diggs]

Grover: What Alex said.

It seems like you have issues beyond doorhangers. But I'd still like to verify if Orca is presenting doorhangers or not. You have a specific site I can try?

Comment 7

[u554753]

Ok, followed the instructions in Comment 5. Firefox is reading the accessibility tool but not reading doorhangers.

To answer Comment 6, any direct link to a YouTube video when not signed in should work. I was able to get a doorhanger that asks if you want to allow YouTube to autoplay media and sound, and the doorhanger does not read that.

https://www.youtube.com/watch?v=z2VZ_OGz0RU

Comment 8

[u554753]

Correction to second part of Comment 7, 

The screenreader does not read the doorhanger.

Comment 9

[Joanmarie Diggs]

Thanks!

Comment 10

[Joanmarie Diggs]

(In reply to Grover Wimberly IV [:Grover-QA] from comment #7)
> Ok, followed the instructions in Comment 5. Firefox is reading the
> accessibility tool but not reading doorhangers.
> 
> To answer Comment 6, any direct link to a YouTube video when not signed in
> should work. I was able to get a doorhanger that asks if you want to allow
> YouTube to autoplay media and sound, and the doorhanger does not read that.
> 
> https://www.youtube.com/watch?v=z2VZ_OGz0RU

I just did a quick test using Orca master and Firefox nightly and Orca presents the doorhanger as an "alert". Mind you, it's not the first thing Orca says, but it is presented. Are you saying it's not presented for you at all? If that is the case, could you try with Orca master and/or Firefox nightly? If you cannot, perhaps Alex could?

Comment 11

[Joanmarie Diggs]

BTW, the reason Orca doesn't present the doorhanger first is that Orca doesn't know about it. The accessibility events we get and which users would expect Orca to present include:

* busy event indicating the youtube page is loading
* a focus event for a clickable object (Orca has to trust focus events are valid
* a focus event for the you tube player
* a showing event with role alert for the doorhanger

Comment 12

[James Teh [:Jamie]]

(In reply to Joanmarie Diggs from comment #10)
> I just did a quick test using Orca master and Firefox nightly and Orca
> presents the doorhanger as an "alert".

(In reply to Joanmarie Diggs from comment #11)
> BTW, the reason Orca doesn't present the doorhanger first is that Orca
> doesn't know about it.

I'm a bit confused between these two comments. If Orca doesn't present it first, when does it currently present it? Only when it's explicitly focused, or automatically, but after other pieces of information?

> The accessibility events we get and which users would
> expect Orca to present include:
> * busy event indicating the youtube page is loading
> * a focus event for a clickable object (Orca has to trust focus events are
> valid
> * a focus event for the you tube player
> * a showing event with role alert for the doorhanger

Are these the events you get now or the events you need? is there an event we're not firing that we should be firing?

Note that these doorhangers don't get focus by default; the user has to press f6 to focus them. However, we want screen readers to report that they're present so users know there's a notification they can choose (or not choose) to interact with.

Thanks!

Comment 13

[Joanmarie Diggs]

(In reply to James Teh [:Jamie] from comment #12)
> (In reply to Joanmarie Diggs from comment #10)
> > I just did a quick test using Orca master and Firefox nightly and Orca
> > presents the doorhanger as an "alert".
> 
> (In reply to Joanmarie Diggs from comment #11)
> > BTW, the reason Orca doesn't present the doorhanger first is that Orca
> > doesn't know about it.
> 
> I'm a bit confused between these two comments. If Orca doesn't present it
> first, when does it currently present it? Only when it's explicitly focused,
> or automatically, but after other pieces of information?

The latter.

> > The accessibility events we get and which users would
> > expect Orca to present include:
> > * busy event indicating the youtube page is loading
> > * a focus event for a clickable object (Orca has to trust focus events are
> > valid
> > * a focus event for the you tube player
> > * a showing event with role alert for the doorhanger
> 
> Are these the events you get now or the events you need? is there an event
> we're not firing that we should be firing?

They are the events we get now. The final one was added so that Orca would present the doorhanger. Orca presents the doorhanger, so I'm not sure why the reporter is not seeing that -- unless they are hearing presentation of the loading event, the two focus events, and not waiting for Orca to present the contents of the doorhanger.

> Note that these doorhangers don't get focus by default; the user has to
> press f6 to focus them. However, we want screen readers to report that
> they're present so users know there's a notification they can choose (or not
> choose) to interact with.

Yup. That's why Orca presents it. :)

Comment 14

[James Teh [:Jamie]]

Thanks Joanie. I just wanted to make sure we were doing the right thing. :)

Comment 15

[u554753]

Apologies for the wait on this comment. After waiting for all of the other previous reads to go off, it does read the doorhanger. Going to close as INVALID.