Oh, digging more in about:config I found out the accessibility.AOM.enabled set as false. Since AOM means Acessibility Object Model, I should set this to true to use with a screen reader? I'll try.Best,Em ter, 4 de abr de 2017 às 09:01, Germano Corrêa <germanobruscato gmail com> escreveu:Thanks a lot for the help!Hi!I looked into about:config and I saw nothing relevant. And yes, I tried switching tabs, it just stops reading when focus firefox window. Once that used to happen with firefox stable, in Ubuntu, but now in Fedora is only happening with Firefox Developer Edition (it might be because I installed with flatpak?). Anyway, firefox stable (the one provided by the distribution official repository) appears to work normally with Orca, so I think I might test stuff with it and not with the Dev Edition.Em seg, 3 de abr de 2017 às 18:57, Jeremy Lincicome <w0jrl1 gmail com> escreveu:Germano,
When in the Firefox window, after you start Orca, have you tried just using alt tab to move out of and then back into the window? I wonder if that will work for you.
Thanks,
Jeremy.On Apr 3, 2017 8:33 AM, <chrys linux-a11y org> wrote:Howdy,
I think this rather an problem in orca and more a heuristic in firefox to disable AT Toolkit support if not needed to save Performance. if no AT (like an screenreader or magnifier) was detected if you run firefox or Thunderbird they assume that you dont need it.
I think, but not totaly sure, this can be forced in about:config in firefox.
Cheers chrys
Am Mo. Apr. 3 15:31:49 2017 GMT+0200 schrieb Germano Corrêa:
> Hello!
>
> Since I work with web accessibility, most of my job consists in evaluting
> accessibility in a website, which includes tests with a screen reader. As I
> use Fedora, the used screen reader is Orca.
>
> I don't know why, but I can't use Orca if I start the screen reader after a
> window is already opened. If I'm using Firefox, for instance, without the
> screen reader, and then I have to start the screen reader to test
> something, it reads nothing in the page, not even the title of the window.
> I have to close Firefox, start Orca, and then open Firefox again.
>
> Sometimes not even this works, with Firefox Developer Edition, for example.
> As I installed it with Flatpak, I don't know if this is an issue related to
> flatpak or if it's just an Orca bug.
>
> The only thing I can think is start Orca on boot, but then disable speak,
> and enabling it when I need, but I'll have to get more used to Orca's
> shortcuts because I can't use Caps Lock normally, for instance, among other
> things.
>
> I would really appreciate it if anyone could help me with this, with a
> workaround or a fix, or just an explanation.
>
> 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
Log bugs and feature requests at http://bugzilla.gnome.org
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
Log bugs and feature requests at http://bugzilla.gnome.org