Re: [orca-list] OT: QT5 accessibility without qt-at-spi

[Jude DaShiell <jdashiel panix com>]

Apple figured out an answer to this question upon release of os 10.04
Tiger.  It may not be the best method but it sure worked for me.  I'm
one of those blind bat lifers since the eyes never developed enough to
see anything.  When I got an Apple Mini I was alone and unpacked it and
hooked up speakers a video monitor keyboard and power to the unit and
hit the on button.  Nothing happened.  I found two DVD's in the box and
put one of them into the combo drive and the computer promptly ejected
that DVD.  I put the second DVD in the drive and it started spinning up
and all the sudden VoiceOver comes on and asks me a question which I
answer with the keyboard.  Apple normally puts that question up on the
screen first from what I've been told and waits a certain amount of time
and if the question doesn't get answered then uses VoiceOver to ask the
question.  Before I got that Mac Mini negative accessibility reviews had
appeared in at least one of National Federation Of The Blind consumer
publications and I sent email to one of the lists about my installation
success and got contacted by the organization's lawyer.  My installation
success prompted an investigation by the Federation's technical lab
which replicated my installation success and cancelled plans to sue
Apple for an inaccessible operating system.

On Fri, 3 May 2019, chrys wrote:

> Date: Fri, 3 May 2019 05:01:08
> From: chrys <chrys linux-a11y org>
> To: Frederik Gladhorn <gladhorn kde org>, orca-list gnome org
> Subject: Re: [orca-list] OT: QT5 accessibility without qt-at-spi
>
> Howdy Frederik,
>
> oh, thanks for clarification. for me it seems not to work without having
> QT_LINUX_ACCESSIBILITY_ALWAYS_ON set.
> I think we should unify the behave to other desktops/ frameworks.
> If i m right GNOME is getting a string from dconf.
>
> dconf gsettings set org.gnome.desktop.a11y.applications screen-reader-enabled
> true
>
> but maybe this is hard to implement for QT as it is a GTK/ GNOME tool?
> what do others think here? Whats the best way to detect if A11y is needed?
>
> cheers chrys
>
> Am 02.05.19 um 10:54 schrieb Frederik Gladhorn:
> > On onsdag 1. mai 2019 18:51:51 CEST chrys wrote:
> > > Howdy,
> > >
> > > the bridge is not needed for QT5 anymore.
> > > you need to set this for QT5
> > > export QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1
> > Technically this is a hack (QT_LINUX_ACCESSIBILITY_ALWAYS_ON) and should not
> > be needed. But it seems like the settings that Qt tries to read, to detect
> > if
> > Orca is running have changed.
> >
> > Is there a sensible way to detect if accessibility is wanted, and to which
> > level? Qt can do all of this on demand and does enable some things only on
> > demand since they come with a slight overhead.
> >
> > Cheers,
> > Frederik
> >
> >
> >
> > > the variable QT_ACCESSIBILTY is AFAIK for QT4
> > >
> > > i have set both and QT is accessible.
> > >
> > > here my accessibility related variables in bashrc (some of them are
> > > quite old lol)
> > >
> > > export OOO_FORCE_DESKTOP=gnome
> > > export SAL_USE_VCLPLUGIN="gtk"
> > > export GTK_MODULES="gail:atk-bridge" # for GTK2
> > > export GNOME_ACCESSIBILITY=1
> > > export QT_ACCESSIBILITY=1 # for QT4
> > > export QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 # for QT5
> > >
> > > maybe this helps,
> > >
> > > cheers
> > >
> > > Am 01.05.19 um 18:23 schrieb Vojt?ch Pol??ek via orca-list:
> > > > Hello,
> > > >
> > > > I am running Arch Linux and I have recently removed qt-at-spi because I
> > > > thought that it is needed only for QT4 applications and I use only QT5
> > > > ones. However, after this QT5 apps stopped being accessible as well. Do
> > > > I need it still?
> > > >
> > > > I have the:
> > > >
> > > > QT_ACCESSIBILITY=1
> > > >
> > > > environment variable set but no luck. Anything else to be done? Or do I
> > > > need to install qt-at-spi again?
> > > >
> > > > Thanks,
> > > >
> > > > Vojta
> > > >
> > > > _______________________________________________
> > > > 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

-- 

_______________________________________________
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