956684 - Firefox and Thunderbird not accessible for Orca screen reader in the LXDE environment

Status: RESOLVED DUPLICATE of bug 743580

(Core :: Disability Access APIs, defect)

Description

[Attila Hammer]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:25.0) Gecko/20100101 Firefox/25.0 (Beta/Release)
Build ID: 20131028112903

Steps to reproduce:

In Ubuntu 14.04 LXDE environment if the GTK_ACCESSIBILITY=1, MOZILLA_ACCESSIBILITY=1 and GTK_MODULES=gail:atk-bridge environments setted for example the /etc/environment file, when Firefox or Thunderbird launched Orca screen reader doesn't reading any content in this two applications.
This is not only Lubuntu specific issue unfortunately, Samuel Thibault experienced similar issue in Debian Wheezy.


Actual results:

After Firefox or Thunderbird launched in Terminal (for example built in Lxterm application), presenting the GTK Accessibility initialized related message and enjoi.
Orca screen reader doesn't functional for example in Firefox and Thunderbird applications.


Expected results:

Need everithing accessible in LXDE environment, similar with GNOME3 environment.

Comment 1

[Attila Hammer]

I experienced similar issue in stable Lubuntu 13.10 release.
The issue is independent with Orca version, I looked now Orca master branch the reported issue.
If need any debugging (log files, etc), please tell me and I generating the required log files.
I tryed this test with Lubuntu 14.04 awailable Firefox 25.0 release.

Attila

Comment 2

[Attila Hammer]

Attachment: debug.out

Joanie, this debug.out file is created with Orca 3.10 version in Lubuntu 14.04, hopefuly show a startup information why not accessible with Firefox and Thunderbird the LXDE environment for Orca.
I simple launched Firefox, and tryed opening a webpage.
Other LXDE applications wonderful accessible in LXDE (gnome-mplayer, lxterm, gnome-system-monitor, gedit, etc).
I tryed looking LXDE a11y preferences and change A11y type with GNOME without good luck.

Attila

Comment 3

[Joanmarie Diggs]

Attila, what that debug.out shows is that Orca is not getting any accessibility events from Firefox.

As for why that is.... I'm not entirely sure. The only thing I can think of that might be different in your non-GNOME environment is the gsettings key for accessibility. Please try the following in a terminal:

gsettings get org.gnome.desktop.interface toolkit-accessibility

Is it true or false? If it's false, quit Firefox (or Thunderbird or whatever Gecko app you're trying to use with Orca). Set it to true in your terminal via:

gsettings set org.gnome.desktop.interface toolkit-accessibility true

Then (re)launch the Gecko app you're trying to use with Orca.

If it was already true, then I'm not sure what the issue is. Hopefully the Mozilla accessibility developers know.

Comment 4

[Attila Hammer]

Joanie, unfortunately we not have luck.
My testing system I setted previous already the org.gnome.desktop.interface toolkit-accessibility setting with true value.

Attila

Comment 5

[Trevor Saunders (:tbsaunde)]

> As for why that is.... I'm not entirely sure. The only thing I can think of
> that might be different in your non-GNOME environment is the gsettings key
> for accessibility. Please try the following in a terminal:

Well, I'd be much more interested in what dbus thinks is happening, in particular what the below prints.

dbus-send --print-reply --type=method_call --dest=org.a11y.Bus /org/a11y/bus org.freedesktop.DBus.Properties.Get string:org.a11y.Status string:IsEnabled

given that's the same thing gecko checks I expect its false, and you need to figure out how to make it be true and then restart firefox / thunderbird.

Comment 6

[Attila Hammer]

Hi Trev,

My Lubuntu session you suggested command returning following output:
method return sender=:1.4 -> dest=:1.56 reply_serial=2
   variant       boolean true

My GNOME3 environment you suggested command returning following output:
method return sender=:1.3 -> dest=:1.90 reply_serial=2
   variant       boolean true

I think both two environment this output is right. You have other ydea?
I don't no important or not, but I using default Openbox window manager and my default session is Lubuntu.

Attila

Comment 7

[Trevor Saunders (:tbsaunde)]

(In reply to Attila Hammer from comment #6)
> Hi Trev,
> 
> My Lubuntu session you suggested command returning following output:
> method return sender=:1.4 -> dest=:1.56 reply_serial=2
>    variant       boolean true
> 
> My GNOME3 environment you suggested command returning following output:
> method return sender=:1.3 -> dest=:1.90 reply_serial=2
>    variant       boolean true
> 
> I think both two environment this output is right. You have other ydea?

Well, given that output I'm pretty suprised firefox isn't enabling accessibility.  All I can really suggest is stepping through mozilla::a11y::ShouldA11yBeEnabled() and seeing what happens.

Comment 8

[Attila Hammer]

Hi Trev,

the MOZILLA_A11y environment value doesn't enabling Mozilla Accessibility if the environment value is defined with 1 value the /etc/environment file?
Testing purpose in Firefox preferences dialog/advanced page I need enabling Accessibility, or you or an another Mozilla developer need enabling default accessibility in the proper component?

Attila

Comment 9

[Trevor Saunders (:tbsaunde)]

(In reply to Attila Hammer from comment #8)
> Hi Trev,
> 
> the MOZILLA_A11y environment value doesn't enabling Mozilla Accessibility if
> the environment value is defined with 1 value the /etc/environment file?

I don't think gecko has ever cared about that.  GNOME_ACCESSIBILITY would I imagine, but you should figure out what's going wrong with the dbus stuff.

> Testing purpose in Firefox preferences dialog/advanced page I need enabling
> Accessibility, or you or an another Mozilla developer need enabling default
> accessibility in the proper component?

I have no clue how to parse that much less what the question is.

Comment 10

[Trevor Saunders (:tbsaunde)]

(In reply to Trevor Saunders (:tbsaunde) from comment #9)
> (In reply to Attila Hammer from comment #8)
> > Hi Trev,
> > 
> > the MOZILLA_A11y environment value doesn't enabling Mozilla Accessibility if
> > the environment value is defined with 1 value the /etc/environment file?
> 
> I don't think gecko has ever cared about that.  GNOME_ACCESSIBILITY would I
> imagine, but you should figure out what's going wrong with the dbus stuff.

GNOME_ACCESSIBILITY=1 being set in the env firefox runs in should work to make firefox be accessible, but the code to check dbus really should just work in lxde kde gnome wherever.

> > Testing purpose in Firefox preferences dialog/advanced page I need enabling
> > Accessibility, or you or an another Mozilla developer need enabling default
> > accessibility in the proper component?
> 
> I have no clue how to parse that much less what the question is.

If your asking if anything special should be done in firefox no, the dbus code should just work as I under stand things.  As for why it doesn't I'm not really sure I guess you need to debug it ;)

Comment 11

[Attila Hammer]

Hi Trevor,

I think I founded a possible workaround after I get a letter from a Debian user, he using Debian Testing.
He wrote following me:
"The problem is an issue with the gtk module import path. The fix
for me in debian testing was to copy the modules directory from
/usr/lib/x86_64-linux-gnu/gtk-2.0/ to /usr/lib/gtk-2.0."
I simple ran following commands:
1. sudo su
2. cd /usr/lib
3. ln -s i386-linux-gnu/gtk-2.0 .

I don't no why, but this commands works too. After this commands Firefox and Thunderbird accessible too the LXDE environment.
Why not founding Firefox and Thunderbird the proper GTK modules if not created the simbolic links?
What the next step your openion?

Attila

Comment 12

[Jarek Czekalski]

Duplicate of #743580
https://bugzilla.mozilla.org/show_bug.cgi?id=743580