Re: [orca-list] Orca master and Firefo nightly

[Joanmarie Diggs <jdiggs igalia com>]

It is technically possible to dive into the accessibility tree and look 
for things which possibly should be presented as the name. But doing so 
runs the risk of the screen reader presenting the wrong thing.

NVDA might be trying to compensate for this bug, but the proper place to 
fix it is in the browser itself so all users get the very same result 
regardless of what operating system, browser, and screen reader they 
happen to use.

--joanie

On 6/2/20 15:12, Alex ARNAUD via orca-list wrote:
> Le 02/06/2020 à 18:08, Joanmarie Diggs a écrit :
> > Alex: To clarify, what are you seeing with Chrome Unstable? For me, 
> > Orca announces the play button for Chrome but it doesn't for Firefox.
> Right, I just want to say I confirm the same behaviour as Jean-Philippe.
>
> > Jean-Philippe: The reason why it works in Chrome is that in Chrome the 
> > push button has an accessible name. But in Firefox, the push button 
> > does not have an accessible name.
> >
> > Push buttons are supposed to have accessible names calculated by the 
> > browser, taking the name from author (Vimeo didn't provide a name) or 
> > the content (there is a child element with a name). Therefore please 
> > file a bug against Firefox for this.
> I don't really understand what is happening here. On Windows, it works 
> correctly on Firefox 77 with NVDA but not with Jaws. So do you mean you 
> have no way to get the name or just the name is not reported at the 
> correct place?
>
> Best regards.
>
> _______________________________________________
> 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