Nabble - kde-accessibility

Announce: AT-SPI2 0.1.3 released.

2009-11-30T09:28:06Z

AT-SPI2 0.1.3 is now available for download at:

http://download.gnome.org/sources/pyatspi/0.1/
http://download.gnome.org/sources/at-spi2-core/0.1/
http://download.gnome.org/sources/at-spi2-atk/0.1/

Notes
=====

This is a development release of AT-SPI2, it has some unfinished
features.

A list of work required before the a full release can be found at:

http://live.gnome.org/Accessibility/BonoboDeprecation

What's changed in AT-SPI2 0.1.3
===============================

Pyatspi:
* Change method names to comply with D-Bus specification.

* API changes needed for out-of-process accessible objects.

* Re-introduction of re-entrant D-Bus methods using pool of
gobject main loops.

* Remove incorrect configure dependency on dbind and droute.

Core:
* Change method names to comply with D-Bus specification.

* API changes needed for out-of process accessible objects.

Atk:
* Change method names to comply with D-Bus specification.

* Support for AtkSocket and AtkPlug.

* API changes needed for out-of process accessible objects.

* Fix for event details - have the generic event handler pass
on details when present.

What is AT-SPI2
===============

AT-SPI2 is a D-Bus based accessibility framework. It defines a D-Bus
protocol for providing and accessing application accessibility
information. The project includes a library for bridging the D-Bus
protocol to the ATK API, allowing Gtk based applications to be made
accessible. It also contains a client (AT) side library in Python.

Where can I get more information about AT-SPI2
==============================================

The project wiki is available at:

http://www.linuxfoundation.org/en/Accessibility/ATK/AT-SPI/AT-SPI_on_D-Bus

A page detailing the project plan can be found at:

http://live.gnome.org/Accessibility/BonoboDeprecation

How can I contribute to AT-SPI2?
================================

AT-SPI2 is currently a small but valuable project. We are actively
seeking new contributors, all help is greatly appreciated. If
interested, please get in touch via:

IRC : 'atspidbus' on Gimpnet
E-Mail: accessibility-atspi@...

Development repositories can be found at:

git://git.gnome.org/pyatspi2
git://git.gnome.org/at-spi2-core
git://git.gnome.org/at-spi2-atk

_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Screen scanner

2009-11-26T09:39:41Z

Hi everyone!

I'm developing a multimodal screen scanner for GNU/Linux in Qt4. Code can be accessed via Git, although I haven't made any release yet as the application isn't reliable enough at the moment.

The website of the project is http://sourceforge.net/projects/nadir

My goal is to create a screen scanner utility which can be controlled by using a keyboard, a mouse, by grabbing sounds with a microphone or by grabbing physical movements with a webcam. And also make the application itself as fully accessible as possible.

Any suggestion, idea, guideline, help... is most welcome.

Regards,
Juan

_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Announce: AT-SPI2 0.1.2 released.

2009-11-16T10:50:43Z

AT-SPI2 0.1.2 is now available for download at:

http://download.gnome.org/sources/pyatspi/0.1/
http://download.gnome.org/sources/at-spi2-core/0.1/
http://download.gnome.org/sources/at-spi2-atk/0.1/

Notes
=====

This is a development release of AT-SPI2, it has some unfinished
features.

A list of work required before the a full release can be found at:

http://live.gnome.org/Accessibility/BonoboDeprecation

What's changed in AT-SPI2 0.1.2
===============================

Pyatspi2:
* Add check using PID to check that the application
using pyatspi does not call itself. This is because the
D-Bus calls are not currently re-entrant.

* Add a non-cached version.

* Refactoring for a more configurable pyatspi.

* New repository created as pyatspi moved from at-spi2-atk.

Fixes (Core):
* Add participation in Gnome session management.

* Remove the droute calls the registry daemon now only
depends on libdbus. Move the dbind and droute libraries
to at-spi2-atk.

* Change the name of the registry daemon so that it does not
conflict with the CORBA version.

* Remove the .service file as the registryd is started
by D-Bus activation.

* Remove libdbind calls from the registryd. Remove libdbind
from LDADD.

Fixes (ATK):
* Add the droute and dbind libraries as static libraries
within this repository. Previously these were shared
libraries in at-spi2-core.

* Add --enable-relocate option

This option is similar to what we did for AT-SPI/CORBA.
The default value is to not enable relocation. If
enabled, however, the atk-bridge module is relocated and a
*.desktop file is installed to initialize GTK_PATH in
gnome-session so the new module can be found by GTK+.

* Only install *.desktop file if GTK_MODULE_DIR is used for
relocating

* Fix gtk_module_init to always return a value

* Abort loading the module if NO_AT_BRIDGE is set and non-0.
Ported from CORBA at-spi.

* Remove cspi from the builds as it is not currently
functional.

* Add desktop file so that the ATK bridge GTK modules
environment variable is set properly by Gnome-session.

* Update the accessible adaptor for use without client side
caching. Add a method to get the interfaces supported by
an accessible.

* Remove pyatspi and the pyatspi tests that have been moved
out into a separate repository.

* Add missing headers.
Fix marshalling state set of accessible objects.

* Remove memory leaks cause by non de-referenced messages.

What is AT-SPI2
===============

AT-SPI2 is a D-Bus based accessibility framework. It defines a D-Bus
protocol for providing and accessing application accessibility
information. The project includes a library for bridging the D-Bus
protocol to the ATK API, allowing Gtk based applications to be made
accessible. It also contains a client (AT) side library in Python.

Where can I get more information about AT-SPI2
==============================================

The project wiki is available at:

http://www.linuxfoundation.org/en/Accessibility/ATK/AT-SPI/AT-SPI_on_D-Bus

A page detailing the project plan can be found at:

http://live.gnome.org/Accessibility/BonoboDeprecation

How can I contribute to AT-SPI2?
================================

AT-SPI2 is currently a small but valuable project. We are actively
seeking new contributors, all help is greatly appreciated. If
interested, please get in touch via:

IRC : 'atspidbus' on Gimpnet
E-Mail: accessibility-atspi@...

Development repositories can be found at:

git://git.gnome.org/pyatspi2
git://git.gnome.org/at-spi2-core
git://git.gnome.org/at-spi2-atk

_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Announce: AT-SPI2 0.1.1 released.

2009-08-14T00:30:40Z

AT-SPI2 0.1.1 is now available for download at:

https://projects.codethink.co.uk/index.php/p/at-spi2/downloads/

Notes
=====

This is a development release of AT-SPI2, it has some unfinished
features.

A list of work required before the a full release can be found at:

http://live.gnome.org/Accessibility/BonoboDeprecation

What's changed in AT-SPI2 0.1.1
==============================

Fixes (Core):
* Replace use of dbind_emit_signal with direct libdbus
call in application cache update.
Fix for bug:
http://bugs.freedesktop.org/show_bug.cgi?id=23029

* Fix problem with signature assignment and iter
initialization in dbind signal sending.

* Modify the incorrect use of dbind_emit_signal_va.
Check for NULL args in dbind_marshall_any.
Fix for bug:
http://bugs.freedesktop.org/show_bug.cgi?id=23027

* Remove *.pc files from source tarballs.

* Remove python check from configure.ac.
Python is not needed for at-spi2-core.

* Link DRoute against D-Bus GLib.

Fixes (ATK):

* Add ATK libraries to cspi LIBADD.
Fixes build problems on OpenSUSE.

* Removal of Accessible objects is now handled properly.
Object removal causes signal to be emitted.

* Fix signature of keyboard event registration
when key array is empty.

What is AT-SPI2
===============

AT-SPI2 is a D-Bus based accessibility framework. It defines a D-Bus
protocol for providing and accessing application accessibility
information. The project includes a library for bridging the D-Bus
protocol to the ATK API, allowing Gtk based applications to be made
accessible. It also contains a client (AT) side library in Python.

Where can I get more information about AT-SPI2
==============================================

The project wiki is available at:

http://www.linuxfoundation.org/en/Accessibility/ATK/AT-SPI/AT-SPI_on_D-Bus

A page detailing the project plan can be found at:

http://live.gnome.org/Accessibility/BonoboDeprecation

How can I contribute to AT-SPI2?
================================

AT-SPI2 is currently a small but valueable project. We are actively
seeking new contributors, all help is greatly appreciated. If
interested, please get in touch via:

IRC : 'a11y' on Gimpnet
E-Mail: accessibility-atspi@...

Development repositories can be found at:

git://anongit.freedesktop.org/at-spi2/at-spi2-atk
git://anongit.freedesktop.org/at-spi2/at-spi2-core

_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Announce: AT-SPI2 0.1.0 released.

2009-07-31T09:09:28Z

AT-SPI2 0.1.0 is now available for download at:

https://projects.codethink.co.uk/index.php/p/at-spi2/downloads/

Notes
=====

This is a development release of AT-SPI2, it has some unfinished
features.

A list of work required before the a full release can be found at:

http://live.gnome.org/Accessibility/BonoboDeprecation

What is AT-SPI2
===============

AT-SPI2 is a D-Bus based accessibility framework. It defines a D-Bus
protocol for providing and accessing application accessibility
information. The project includes a library for bridging the D-Bus
protocol to the ATK API, allowing Gtk based applications to be made
accessible. It also contains a client (AT) side library in Python.

Where can I get more information about AT-SPI2
==============================================

The project wiki is available at:

http://www.linuxfoundation.org/en/Accessibility/ATK/AT-SPI/AT-SPI_on_D-Bus

A page detailing the project plan can be found at:

http://live.gnome.org/Accessibility/BonoboDeprecation

How can I contribute to AT-SPI2?
================================

AT-SPI2 is currently a small but valueable project. We are actively
seeking new contributors, all help is greatly appreciated. If
interested, please get in touch via:

IRC : 'a11y' on Gimpnet
E-Mail: accessibility-atspi@...

Development repositories can be found at:

git://anongit.freedesktop.org/at-spi2/at-spi2-atk
git://anongit.freedesktop.org/at-spi2/at-spi2-core

_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Re: Is this a kaccess bug?

2009-07-24T18:29:38Z

Hi again
I've created a patch to evade the application of exit when the dialog is closed, I do it by calling setQuitOnLastWindowClosed(false).

Is ok for you to commit it?

Thx!

On Fri, Jul 24, 2009 at 4:12 PM, Alex Fiestas <alex@...> wrote:

Hi
When you push 5 times shift a dialog appear asking you a few things.
If you click "No", the dialog disappear and kaccess dies :/

Is that the behavior kaccess is supposed to have? If kaccess dies then the dialog doesn't appear again (even if I choose this option from the dialog), so that sounds odd to me.

Thanks!

[kaccess.patch]

Index: main.cpp =================================================================== --- main.cpp (revision 1001464) +++ main.cpp (working copy) @@ -42,7 +42,11 @@ return 1; } kDebug() << "X server XKB extension major=" << major << " minor=" << minor; - + + //This application have a ui that is visible only some times, we've to evade + //The application of exit when the last window is closed. + app.setQuitOnLastWindowClosed(false); + app.setXkbOpcode(xkb_opcode); app.disableSessionManagement(); return app.exec();

_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Is this a kaccess bug?

2009-07-24T09:12:16Z

Hi
When you push 5 times shift a dialog appear asking you a few things.
If you click "No", the dialog disappear and kaccess dies :/

Is that the behavior kaccess is supposed to have? If kaccess dies then the dialog doesn't appear again (even if I choose this option from the dialog), so that sounds odd to me.

Thanks!

_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Re: Simon Listens

2009-07-16T13:06:37Z

Hi Folks,

just to let u know, the HADI-BOMP has moved!
New Location is at:
http://www.sk.uni-bonn.de/forschung/phonetik/sprachsynthese/bomp/bomp-license-
terms

Ralph.

Am Dienstag 14 Juli 2009 16:12:19 schrieb Peter Grasch:

> Hi Olaf!
>
> > I used to be one of the main KDE Accessibility people (but do not have
> > enough time left to continue with it), so I appreciate it very much
> > whenever other people write accessibility software for KDE and continue
> > this much needed work.
>
> Thank you. I am subscribed to the kde-acessibility and the
> gnome-accessibility mailing lists and have found the gnome one to be way
> more active...
>
> I agree that accessibility is a very important factor and hopefully simon
> can contribute to make KDE and the Linux desktop a little bit more
> accessible.
>
> > The KDE promo team is currently discussing how to wrote the dot story,
> > and are very interested in interviewing a developer. I am sending this
> > reply to both mailing lists, so that you can discuss this directly.
>
> Of course. They are very welcome to contact me on this e-Mail address (I am
> not subscribed to their mailing list).
>
> Greetings,
> Peter
> _______________________________________________
> kde-accessibility mailing list
> kde-accessibility@...
> https://mail.kde.org/mailman/listinfo/kde-accessibility

_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Re: Reworking the kwin tabbox

2009-07-16T12:10:10Z

On Thursday 16 July 2009 16:59:44 Martin Gräßlin wrote:

> So now my ideas what a new implementation could provide. Sorry no
> mockups

Please, add mockups :-). Unless you like to hear comments of what
other subscribers think of their guesses. I see mockup, I am 100%
sure what I am talking about.

> * On the fly switching of sorting strategy (e.g. only apps of
> current desktop, all desktops,

Cool.

> * Highlight windows effect support for currently selected window

Not sure what you mean -- you have to show selection.

> * Thumbnail of currently selected window

Please, make this optional. While thumbnails of course provide
information, they also provide too many information. I am happy with
KDE3 switcher (except for bigger icons, horizontal orientation and
being 100% reliable).

> * When desktop switching extend the selected item to show windows
> on the desktop as subitems -> direct switching to a client

Could you explain this more, I don't understand what you mean.

> * Make it possible to have effects and tabbox as well with
> different shortcuts
> * Effects need to be able to switch the sorting
> as well
> * Searching in effects

What is effect and sort here? Before you used term sort in sense of
scope. And now?

> * Why do we have to hold the alt key while switching? Can't we
> break with the concept?

Nope, it's fast.

> What could be
> a better solution than pressing alt?

Not better -- different. You can use switcher on fly or as permanent
one. Let's denote down by v, and up by ^.

alt v, tab v (for 3 seconds), tab ^, alt ^

or

F7 v, F7 ^, tab v (for 3 seconds), tab ^, enter v, enter ^

in other words on fly switcher is activated by some shortcut which has
to be hold all the time, and releasing it means commit-switch. Or
switcher can be triggered on, and commit has to be done explicitly
(by pressing enter for example).

F7 above of course is just an example.

Both ways are useful, valid and should be supported. Just basic
reasons:
first one -- for healthy power-users
second one -- for handicapped users

> More
> ideas are welcome :-)

Well, no ideas here, I only need KISS switcher -- horizontal/vertical
(option) list with icon/thumbnail (option) and labels. With two modes
of switching (permanent and on-fly). 100% reliable. That's all.

Of course I am talking about _basic_ switcher, not expose switcher or
anything like that.

Cheers,
_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Re: Simon Listens

2009-07-14T07:11:27Z

Hi Olaf!

> I used to be one of the main KDE Accessibility people (but do not have
> enough time left to continue with it), so I appreciate it very much
> whenever other people write accessibility software for KDE and continue
> this much needed work.
Thank you. I am subscribed to the kde-acessibility and the gnome-accessibility
mailing lists and have found the gnome one to be way more active...

I agree that accessibility is a very important factor and hopefully simon can
contribute to make KDE and the Linux desktop a little bit more accessible.

> The KDE promo team is currently discussing how to wrote the dot story, and
> are very interested in interviewing a developer. I am sending this reply to
> both mailing lists, so that you can discuss this directly.
Of course. They are very welcome to contact me on this e-Mail address (I am
not subscribed to their mailing list).

Greetings,
Peter
_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Re: Simon Listens

2009-07-14T06:50:46Z

Hi Peter,

thanks for writing this cool software.

I used to be one of the main KDE Accessibility people (but do not have enough
time left to continue with it), so I appreciate it very much whenever other
people write accessibility software for KDE and continue this much needed
work.

The KDE promo team is currently discussing how to wrote the dot story, and are
very interested in interviewing a developer. I am sending this reply to both
mailing lists, so that you can discuss this directly.

Olaf

[ Peter Grasch, Dienstag 14 Juli 2009 ]

> Hi!
>
> > I smell a candidate for a really cool dot story.
>
> That would be awesome!
>
> I think simon could already be of great help to some people (who just don't
> know it yet) and of course it can't hurt to expose it to a great community
> of developers :)
>
> There is a release announcement on our blog (if someone is interested):
> http://simon-listens.blogspot.com/2009/07/simon-02-released.html
>
> Greetings,
> Peter (simon developer)

_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

signature.asc (204 bytes) Download Attachment

Re: Simon Listens

2009-07-14T04:17:18Z

Hi!

> I smell a candidate for a really cool dot story.
That would be awesome!

I think simon could already be of great help to some people (who just don't
know it yet) and of course it can't hurt to expose it to a great community of
developers :)

There is a release announcement on our blog (if someone is interested):
http://simon-listens.blogspot.com/2009/07/simon-02-released.html

Greetings,
Peter (simon developer)

Am Montag 13 Juli 2009 21:24:11 schrieb Kevin Krammer:

> Hi all,
>
> just came across this (project website [1])
> http://www.youtube.com/watch?v=x_9ImaiOISs
>
> Awesome!
>
>
> Cheers,
> Kevin
>
> [1] http://simon-listens.org/index.php?id=122&L=1

_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Simon Listens

2009-07-13T12:24:11Z

Hi all,

just came across this (project website [1])
http://www.youtube.com/watch?v=x_9ImaiOISs

Awesome!

I smell a candidate for a really cool dot story.

Cheers,
Kevin

[1] http://simon-listens.org/index.php?id=122&L=1

--
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

signature.asc (196 bytes) Download Attachment

Re: Help Disable people who loves Linux

2009-06-09T11:09:03Z

On Monday 08 June 2009 17:21:24 Aymeric van Puyvelde wrote:

> I can't no more use Ubuntu, because there is no tools available to
> move mouse pointer except http://viacam.org wich doesn't work.

I just tested it (opensuse here) and initially it does not work, but I
got quick response from developers how to make it run. Install it
first of course, and then in your home directory, create file
.eviacam
edit it, and add the line:
openClickWinAtStartup=0

With such settings it works for me (using KDE 3.5.10). However you
have to move your head, not eyes, to control the cursor, I don't know
if you are capable to do this.

> this software <http://nipg.inf.elte.hu/headmouse/headmouse.html> is
> the best open-source for windows.
> sources are here <http://sourceforge.net/projects/erutarian>
> is it posssible for a team to port it ?

I am sorry but for now I cannot help with this.

Cheers,
_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Help Disable people who loves Linux

2009-06-08T08:21:24Z

Hello all

I'm french, 33 years old and father of a young sweet baby.
I'm daily using this software in order to manage my computer by moving the mouse with my head moves throught a usb webcam, I became disable due to a desease: ALS.
I can't no more use Ubuntu, because there is no tools available to move mouse pointer except http://viacam.org wich doesn't work.
this software is the best open-source for windows.
sources are here
is it posssible for a team to port it ?
but I'm not a dev just a script maker..
Thank you for your time and your atttention

--
Aymeric aka Kilhian
_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

kttsd using speech-dispatcher

2009-06-05T07:02:40Z

Gary,

I hope all is well with you. As you may or may not know I've been working
toward getting kttsd to use speech-dispatcher exclusively for it's speech
synthesis and have a couple of questions for you. I'm not sure if you are
allowed to give advice in this regard, if not please let me know and I'll
continue to get help from other KDE devs.

I've been porting ktts using the speech-dispatcher C API and it has been
working alright so far. I removed all the plugins completely, and combined
speechdata and speaker classes into one class, made it a singleton, and it
uses the C API to talk to speech-dispatcher. I've commented out the filtering
for now, as I'm not sure how that will work. speech-dispatcher gives us a job
number when we tell it to say something, so I'm wondering about possibly
having our joblists in kttsd not tied directly to those in speech-dispatcher,
so one SpeechJob can send each sentence as a separate say request. This would
mean we'd need to handle priority of jobs ourselves also though, which speech-
dispatcher already handles internally for all requests it receives.

So, I think I've got 2 options.
1. continue to make SpeechJob's directly correlate to speech-dispatcher jobs
and do the filtering synchronously as they come in to kttsd via the dbus
connection.

2. make SpeechJob's keep a speech-dispatcher jobnum internally, and keep a
mapping of speech-dispatcher job numbers to our speechjob numbers to use when
notifications come from speech-dispatcher about it's job's state changes.

Any advice about either option?

thanks,
Jeremy
_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

KTTS Help Hadifix update

2009-06-04T16:32:10Z

If you do not already have Hadifix installed, do this:
1. Download MBROLA binary from http://tcts.fpms.ac.be/synthesis/mbrola.html
2. Install MBROLA to /usr/local/mbrola folder.
3. Download at least one german language file from the MBROLA site. Unzip to
the /usr/local/mbrola folder.
4. Download txt2pho from http://www.ikp.uni-
bonn.de/forschung/phonetik/sprachsynthese/txt2pho
5. Unzip txt2pho to /usr/local/txt2pho.
6. Edit txt2phorc file, putting correct data paths in.
7. Either copy txt2phorc to ~/.txt2phorc or to /etc/txt2pho. Note that you
drop the "rc" in file name.
8. In kttsmgr, choose Add/Hinzufügen, Language/Sprache = Deutsch, Synthesiser
= Hadifix.
9. On the Configure Talker screen, configure a voice and the paths to MBROLA and
txt2pho. For German Umlauts to work one need to set encoding to Latin1
10. On Audio-Tab set output to ALSA
11. Back in Configure Talker screen press Test-Button.

OK, this is not really better, but links are fixed.

Regards,
Ralph

_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

AT-SPI on D-bus

2009-06-04T07:34:56Z

Hello guys, does someone know more about the progres of moving AT-SPI to
D-bus? I've even seen that Orca has been made able to use AT-Spi on
D-Bus, but I couldn't find any D-Bus-based version of AT-SPI. Hope
someone knows more,
best regards
Roman
_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

contact removal

2009-05-27T08:04:52Z

hi List.

When i remove a contact from the list, i don't get a confirmation
dialog. That's likely because i checked "do not ask again" before. I
haven't found any way to re-enable this in the interface, i have a
feeling it's somewhere in an xml file since i didn't find anything in
kopeterc. What did i overlook?

Regards, Nick Keefen,

_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Re: Is the KDE accessibility project dead?

2009-05-27T00:12:31Z

Hi Charlie,

> Hi, I was wondering if the KDE accessibility project dead? For years I have
> checked the progress of accessibility for KDE and haven't seen much progress
> for a few years. Is there any work on a screen read similar to Orca in the
> works? Thank you.
> Charlie

As far as I'm concerned the project isn't dead. My aim at least is to be
able to use Orca itself on KDE, rather than write a whole new screen-reader.

My Qt to AT-SPI D-Bus work can be found at
git://doffman.com/qspiaccessiblebridge. Its at an admittedly early
stage, but its getting constant attention. Any help gratefully received,
especially from those with more Qt experience than I.

For AT-SPI D-Bus information go to:

http://www.linuxfoundation.org/en/Accessibility/ATK/AT-SPI/AT-SPI_on_D-Bus

Thanks

Mark
_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Is the KDE accessibility project dead?

2009-05-26T08:59:38Z

Hi, I was wondering if the KDE accessibility project dead? For years I have checked the progress of accessibility for KDE and haven't seen much progress for a few years. Is there any work on a screen read similar to Orca in the works? Thank you.
Charlie

Is the KDE accessibility project is dead?

2009-05-26T08:58:12Z

Hi, I was wondering if the KDE accessibility project is dead? For years I have checked the progress of accessibility for KDE and haven't seen much progress for a few years. Is there any work on a screen read similar to Orca in the works? Thank you.
Charlie

Re: KDE-accessibility/Qt AT-SPI

2009-05-14T03:32:45Z

Hi Dan:

You can learn more about the Orca screen reader and magnifier at
http://live.gnome.org/Orca. I would love to grow the Orca developer
community, so please let me know what questions you may have.

Will

Dan Miner wrote:

> I'm glad to hear that a common ground appears to be coming out the
> work. I'm becoming very interested in accessibility on a personal front
> because I'm nearing the end of my vision. Is there some resources you
> could mention for a developer starting out on building and eventual coding?
>
> I'm a software developer myself and I'm starting to find serious need
> for screen magnification and reading now. Last time I tried, I couldn't
> get the latest code to ever build and then no clues even how to get
> stuff submitted.
>
> Regards,
> Dan
>
>
> Olaf Schmidt wrote:
>> Hi Jeremy,
>>
>> thanks a lot for offering to contribute to KDE Accessibility.
>>
>> As you already wrote, Qt had an accessibility framework that can be used to
>> make Qt and KDE applications accessible with Orca or other assistive
>> technologies. One Trolltech developer (Harald Fernengel) even wrote a D-Bus
>> interface for it:
>> http://labs.trolltech.com/page/Projects/Accessibility/QDBusBridge
>>
>> See also:
>> http://labs.trolltech.com/page/Projects/Accessibility/IAPoke
>> http://labs.trolltech.com/page/Projects/Accessibility/QDasher
>>
>> This interface could be used by Orca. But it would need to be completed and
>> bug-fixed to achieve the full results, and in the meantime, it has become clear
>> Gnome is now also moving to D-Bus for their accessibility framework.
>>
>> It would make a lot of sense to rework Harald's code to use the same D-Bus
>> interfaces as Gnome.
>>
>> The timing is very good to get involved now, since it has become clear at last
>> that a common approach with Gnome is possible. Important decisions about the
>> Free Software accessibility architecture have been made (namely, Gnome's D-Bus
>> move).
>>
>> Gunnar and I spent a lot of time on KDE Accessibility in the past, but we are
>> now at a point where we simply do not have the time any more to continue with
>> this very important work. But I promise to help you as much as I can (by
>> answering questions and maybe by helping with the testing) if you wish to
>> continue with the work started by Harald, Gunnar and myself.
>>
>> Olaf
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> kde-accessibility mailing list
>> kde-accessibility@...
>> https://mail.kde.org/mailman/listinfo/kde-accessibility
>>
>
> _______________________________________________
> kde-accessibility mailing list
> kde-accessibility@...
> https://mail.kde.org/mailman/listinfo/kde-accessibility

_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Re: KDE-accessibility/Qt AT-SPI

2009-05-13T15:59:02Z

I'm glad to hear that a common ground appears to be coming out the
work. I'm becoming very interested in accessibility on a personal front
because I'm nearing the end of my vision. Is there some resources you
could mention for a developer starting out on building and eventual coding?

I'm a software developer myself and I'm starting to find serious need
for screen magnification and reading now. Last time I tried, I couldn't
get the latest code to ever build and then no clues even how to get
stuff submitted.

Regards,
Dan

Olaf Schmidt wrote:

> Hi Jeremy,
>
> thanks a lot for offering to contribute to KDE Accessibility.
>
> As you already wrote, Qt had an accessibility framework that can be used to
> make Qt and KDE applications accessible with Orca or other assistive
> technologies. One Trolltech developer (Harald Fernengel) even wrote a D-Bus
> interface for it:
> http://labs.trolltech.com/page/Projects/Accessibility/QDBusBridge
>
> See also:
> http://labs.trolltech.com/page/Projects/Accessibility/IAPoke
> http://labs.trolltech.com/page/Projects/Accessibility/QDasher
>
> This interface could be used by Orca. But it would need to be completed and
> bug-fixed to achieve the full results, and in the meantime, it has become clear
> Gnome is now also moving to D-Bus for their accessibility framework.
>
> It would make a lot of sense to rework Harald's code to use the same D-Bus
> interfaces as Gnome.
>
> The timing is very good to get involved now, since it has become clear at last
> that a common approach with Gnome is possible. Important decisions about the
> Free Software accessibility architecture have been made (namely, Gnome's D-Bus
> move).
>
> Gunnar and I spent a lot of time on KDE Accessibility in the past, but we are
> now at a point where we simply do not have the time any more to continue with
> this very important work. But I promise to help you as much as I can (by
> answering questions and maybe by helping with the testing) if you wish to
> continue with the work started by Harald, Gunnar and myself.
>
> Olaf
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> kde-accessibility mailing list
> kde-accessibility@...
> https://mail.kde.org/mailman/listinfo/kde-accessibility
>

_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Re: kde-accessibility Digest, Vol 67, Issue 4

2009-05-13T05:18:56Z

Hi Jeremy,

I have been working on a bridge from QAccessible to the D-Bus version of
AT-SPI. If we manage to move Gnome over to D-Bus AT-SPI then it may be
possible for Gnome and KDE to share an accessibility architecture using
this bridge. The current focus of my work is making Qt applications
testable through programs such as Dogtail and LDTP, more work will
certainly be required to make KDE accessible using a screen reader such
as Orca.

The code can currently be found at:

git://doffman.com/qspiaccessiblebridge

Its under heavy development.

I'd really like to get people together at the desktop summit to talk
about a shared accessibility architecture.

Willie Walker has already suggested an Accessibility meeting on the
gnome-desktop-devel lists, unfortunately without much reaction. I'll be
at the Desktop Summit, willing to meet anyone from KDE to talk about
shared a11y. Perhaps we should have a KDE & Gnome a11y get-together.

> Hello,
>
> I've recently become aware of some shortcomings in KDE-accessibility project
> (or possibly only percieved shortcomings). I'm very curious as to the state
> of Qt/KDE with regard to their ability to work with screen reader programs
> such as Orca. Note that I'm not blind, have not used Orca as of yet, but as a
> KDE developer I'm worried that we are not quite as supportive of accessibility
> as we should be and/or used to be. Gunnar posted some specs for how to use ATK
> and/or AT-SPI to the kde accessibility website, but that was years ago.[1] Qt
> also supposedly has accessibility support in Qt 4 [2] but without going to AT-
> SPI I've no clue what good it does, i.e. what interfaces it provides and how
> screen readers such as Orca can use it.

There was a AT-SPI like D-Bus interface created for Qt a few years ago.
It is not the same as the D-Bus interface Gnome are looking to integrate
into 3.0. (It is similar)

This interface does not work with Orca or any of the gnome a11y tools.

>
> From what little research I have done it appears that there is work going on
> to make an AT-SPI to DBus bridge, which is not yet completed from what I
> gather. Please correct me if I'm wrong on any of this, my aim is to start a
> discussion and get some things started or at the very least understand some
> more about this.

Yes its underway, but ATM its specifically for the purposes of desktop
testing, not accessibility. More work will be required to ensure it
functions with AT's such as Orca.

>
> I also noticed that on the Orca site, and all gnome accessibility sites I have
> found Qt/KDE is mentioned as not providing the accessible interface necessary
> for screen readers to work with our apps. I'd like to know if this is true,
> and also how to remedy this. I'll be installing/trying Orca soon to get a
> feel for how it works, and what it does exactly, etc. and so I'll be able to
> test it with KDE/Qt apps.

KDE provides the QAccessible interface, which is probably not
sufficient. QAccessible2 is included in the codebase, but is probably
classed as 'Beta' as it has not been placed in the documentation and
regular changes are being made to it.

The QAccessible -> AT-SPI D-Bus bridge I am working on targets QAccessible2.

ATM there is no way to test Qt apps with Orca, you could attempt it
using my bridge and the D-Bus version AT-SPI. Information on D-Bus
AT-SPI can be found at:

http://www.linuxfoundation.org/en/Accessibility/ATK/AT-SPI/AT-SPI_on_D-Bus

Infact, any help would be much appreciated.

Thanks

Mark
_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Re: KDE-accessibility/Qt AT-SPI

2009-05-13T04:27:48Z

Hi Jeremy,

thanks a lot for offering to contribute to KDE Accessibility.

As you already wrote, Qt had an accessibility framework that can be used to
make Qt and KDE applications accessible with Orca or other assistive
technologies. One Trolltech developer (Harald Fernengel) even wrote a D-Bus
interface for it:
http://labs.trolltech.com/page/Projects/Accessibility/QDBusBridge

See also:
http://labs.trolltech.com/page/Projects/Accessibility/IAPoke
http://labs.trolltech.com/page/Projects/Accessibility/QDasher

This interface could be used by Orca. But it would need to be completed and
bug-fixed to achieve the full results, and in the meantime, it has become clear
Gnome is now also moving to D-Bus for their accessibility framework.

It would make a lot of sense to rework Harald's code to use the same D-Bus
interfaces as Gnome.

The timing is very good to get involved now, since it has become clear at last
that a common approach with Gnome is possible. Important decisions about the
Free Software accessibility architecture have been made (namely, Gnome's D-Bus
move).

Gunnar and I spent a lot of time on KDE Accessibility in the past, but we are
now at a point where we simply do not have the time any more to continue with
this very important work. But I promise to help you as much as I can (by
answering questions and maybe by helping with the testing) if you wish to
continue with the work started by Harald, Gunnar and myself.

Olaf

_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

signature.asc (204 bytes) Download Attachment

KDE-accessibility/Qt AT-SPI

2009-05-11T10:34:37Z

Hello,

I've recently become aware of some shortcomings in KDE-accessibility project
(or possibly only percieved shortcomings). I'm very curious as to the state
of Qt/KDE with regard to their ability to work with screen reader programs
such as Orca. Note that I'm not blind, have not used Orca as of yet, but as a
KDE developer I'm worried that we are not quite as supportive of accessibility
as we should be and/or used to be. Gunnar posted some specs for how to use ATK
and/or AT-SPI to the kde accessibility website, but that was years ago.[1] Qt
also supposedly has accessibility support in Qt 4 [2] but without going to AT-
SPI I've no clue what good it does, i.e. what interfaces it provides and how
screen readers such as Orca can use it.

From what little research I have done it appears that there is work going on
to make an AT-SPI to DBus bridge, which is not yet completed from what I
gather. Please correct me if I'm wrong on any of this, my aim is to start a
discussion and get some things started or at the very least understand some
more about this.

I also noticed that on the Orca site, and all gnome accessibility sites I have
found Qt/KDE is mentioned as not providing the accessible interface necessary
for screen readers to work with our apps. I'd like to know if this is true,
and also how to remedy this. I'll be installing/trying Orca soon to get a
feel for how it works, and what it does exactly, etc. and so I'll be able to
test it with KDE/Qt apps.

thanks,

Jeremy Whiting

P.S. I am subscribed to both cc'ed lists and will join any others as needed.

[1] http://accessibility.kde.org/developer/atk.php
[2] http://doc.trolltech.com/4.5/qt4-accessibility.html
_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Re: No "show keyboard status" indicator in KDE4

2009-05-11T01:26:41Z

2009/5/11 Peter Grasch <grasch@...>:

> Hello!
>
> Wasn't Aaron Seigo working on this (http://aseigo.blogspot.com/2009/04/more-
> on-keyboard-status.html)?
>
> Seems like the hard bits are already worked out...
>
> I'd contact Aaron Seigo (aseigo@...). I don't know if he is reading this
> mailing list...
>

I didn't see that post but I remember an earlier post in which Aaron
mentioned that he is working on the plasmoid because nobody else is
and it fell on him. I did consider contacting Aaron directly, however
this is a much wider issue. That is why I've written to this list,
which appears to me to be the body which handles these issues in KDE.

I very much appreciate Aaron's work and I've told him that in the
past. I am glad to see his work on the plasmoid which nobody else
seems willing to. I do not want to come off unappreciative, because I
am appreciative, but those people which developers like to call
"users" are not so free to get up and leave when things don't suit us.
I have a lot of time and effort invested in KDE, even if I did not
help code it, and switching desktops is to me a bigger issue than
switching operating systems (KDE runs on Windows now and I am
seriously considering switching to Windows with KDE). We come to
depend on our desktops to function either in a specific fashion or to
provide any specific feature. This is where much of the frustration at
KDE 4 seems to stem from: KDE 3 power users who are missing features
in KDE 4. But even worse, is when a critical feature is added, then
removed. This lures the user away from his
unsupported-but-still-working KDE 3 into KDE 4 (a switch that is
generally irreversible due to different types of configurations of
both KDE itself and critical applications), and then leaves him
without the feature that he depends upon.

By the way, google me on lists like the Kubuntu list, the KDE3-jaunty
list, and other mailing lists to see how many people that I've helped
tell me what is missing for _them_ in KDE 4 and have filed feature
requests or bugs. I have done a lot of work to prevent these
situations for tens of people.

--
Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Re: No "show keyboard status" indicator in KDE4

2009-05-11T00:14:33Z

Hello!

Wasn't Aaron Seigo working on this (http://aseigo.blogspot.com/2009/04/more-
on-keyboard-status.html)?

Seems like the hard bits are already worked out...

I'd contact Aaron Seigo (aseigo@...). I don't know if he is reading this
mailing list...

Greetings,
Peter
_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

No "show keyboard status" indicator in KDE4

2009-05-10T23:31:02Z

Currently there is no "show keyboard status" indicator in KDE4:
https://bugs.kde.org/show_bug.cgi?id=165402

The plasmoid was briefly in kdereview but has now been moved back to
playground for this reason (quote from the bug report):
"move back to playground; the UI is horrific, the code is ancient and
apparently it has no developer to be its constant companion"

Is KDE really this irresponsible? I had been stuck on KDE 3 until just
last month, because I depend on this plasmoid. Now that I've taken the
trouble to move to KDE 4 (Kubuntu packaged the kdereview plasmoid by
special request) they are dropping this issue, and leaving me with a
soon-to-be unusable desktop? KDE 3 is unmaintained, so I cannot go
mack there, and KDE 4 lured me in with the promise of support for my
disability and has now left me hanging here.

Seriously, I am bordering between disappointment and anger here. I
have filed over 200 bugs and feature requests with KDE, and triaged
about 400 other bugs for other people, and often I see that minor
visual enhancements and feature requests are handled quickly and
professionally. So why not the accessibility issues?

--
Dotan Cohen

http://what-is-what.com
http://gibberish.co.il
_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Re: Open Solaris

2009-05-01T05:17:57Z

Hi Charlie:

Orca provides the screen reading and magnification capabilities for
OpenSolaris, and the Sun Microsystems team works to make sure
accessibility is integrated properly before the distribution is released.

Since this is the KDE list, however, your question is most likely off
topic for this list. You might try the OpenSolaris
accessibility-discuss list for OpenSolaris-specific questions and the
GNOME orca-list for questions specific to Orca:

http://mail.opensolaris.org/mailman/listinfo/accessibility-discuss
http://mail.gnome.org/mailman/listinfo/orca-list

Will

CERoss Technologies Services wrote:

> Has anyone worked with Open Solaris, I am interested in hearing about it and
> its usefulness along with accessible areas namely magnification and screen
> reading.
>
> Charlie Ross
> I am looking to test such a system along with Ubuntu, Fedora, a version of
> Suse. Although very new to all this I thought I'd just as well jump in all
> at once and hope for a pleasurable learning curve... any mentorship greatly
> appreciated.
>
> _______________________________________________
> kde-accessibility mailing list
> kde-accessibility@...
> https://mail.kde.org/mailman/listinfo/kde-accessibility

_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Open Solaris

2009-04-30T18:19:34Z

Has anyone worked with Open Solaris, I am interested in hearing about it and
its usefulness along with accessible areas namely magnification and screen
reading.

Charlie Ross
I am looking to test such a system along with Ubuntu, Fedora, a version of
Suse. Although very new to all this I thought I'd just as well jump in all
at once and hope for a pleasurable learning curve... any mentorship greatly
appreciated.

_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Loquendo TTS and Ktts

2009-04-23T03:59:04Z

Hi, I'm trying to found out if Loquendo Speech Engine can work with
Ktts. Loquendo TTS comes with a java based GUI and the command line
TTSFileGenerator tool, see below. Any help is very appreciated

Regards Joakim

joakim@vega:/opt/Loquendo/LTTS7/bin$ ./TTSFileGenerator -?
--------------------- TTSFileGenerator -------------------------
Copyright (C) 2008 - Loquendo SpA.
Loquendo TTS Multimedia (LTTS v.7.11.5 Build 16639 - 2009-03-19 11:57:32
+0100 (Thu, 19 Mar 2009))
Multilingual Text-To-Speech Synthesis System.

This program opens a text file and converts each line of text into a
soundfile.
Each input line can contain either an ASCII message, or the name of an
ASCII/UNICODE file on disk (-n option). Supported output formats are:
Microsoft Windows PCM ("wav"), raw data ("raw" or "pcm") and Windows
Media Audio ("asf" or "wma" - Windows only).
If no input file is given, the program reads from standard input.
Output file name can be optionally given in the form of a "prefix" (that
is the
first part of the output filename). The program will append a progressive
counter and the appropriate file extension (.wav, .raw, etc.). If no
prefix is
given, the output file name will be automatically generated.

Usage: ./TTSFileGenerator [options]... [parameters]

Options:
-h /* Shows usage */
-q /* Quiet mode: no output */
-n /* Each line of the input file is a the name of a text file to read */
-v <Speaker name (default: Ludoviko)>
-l <Language (default: Speaker's mother tongue)>
-c <Speech Coding (a=PCM A-law, u=PCM u-law, l=PCM linear [default])>
-f <Speech Sample Rate (default: 32000Hz)>
-s <Number of audio channels (1:mono, 2:stereo, default:1)>
-o <Output file prefix: [=filename]>
-e <Output file extension (e.g.: wav [default], raw, asf [Windows only]>
Parameters:
Input Filename (default:stdin)

_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Re: Full Screen Magnification

2009-04-18T06:47:48Z

Am Saturday, 18. April 2009 15:20:37 schrieb Maciej Pilichowski:

> On Saturday 18 April 2009 15:05:08 Stephan Johach wrote:
> > > Fullscreen is already there, and it is not working.
> >
> > Are you talking about KDE 4?
>
> Yes.
>
> > I have Desktop Zoom working (KDE 4.2),
>
> I am talking about KMag. I choose fullscreen and the image is frozen.

Yes, KMag seems broken with fullscreen mode. Try the Desktop Zoom.

I already filed a wish list item to get the zoom factor saved between
sessions. If anybody else want to comment on this here is the url

https://bugs.kde.org/show_bug.cgi?id=189956

> > It needs composite (dri) enabled, so you need
> > a supported video card/driver.
>
> I believe I have one, everything else works without problem.

The dri I talked about is needed for the kwin effects. KMag should
work without them. So if you have something to complain about
zooming in KDE 4 you should file a bug report against kwin (see above).

I am currently trying to get the Track Mouse effect working. But
nothing happens when pressing Ctrl+Meta. I guess everything
using Meta key is broken here. :/

Regards,
Stephan

--
"My definition of good literature is that which can be read by an educated
reader, and reread with increased pleasure."
- Gene Wolfe

_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility

Re: Full Screen Magnification

2009-04-18T06:20:37Z

On Saturday 18 April 2009 15:05:08 Stephan Johach wrote:

> > Fullscreen is already there, and it is not working.
>
> Are you talking about KDE 4?

Yes.

> I have Desktop Zoom working (KDE 4.2),

I am talking about KMag. I choose fullscreen and the image is frozen.

> It needs composite (dri) enabled, so you need
> a supported video card/driver.

I believe I have one, everything else works without problem.

Cheers,
_______________________________________________
kde-accessibility mailing list
kde-accessibility@...
https://mail.kde.org/mailman/listinfo/kde-accessibility