'Re: KDE accessibility'

[prev in list] [next in list] [prev in thread] [next in thread] 

List: kde-devel
Subject: Re: KDE accessibility
From: Jeremy Whiting <jpwhiting () kde ! org>
Date: 2010-08-19 21:14:09
Message-ID: AANLkTi=UevMhmKQwo7Hx5uJ3CE5Q9tHVHttGTd4ixyqf () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]

On Sat, Aug 14, 2010 at 8:42 AM, Franklin <franklin@goodhorse.idv.tw> wrote:

> Hi list,
>
> Today I attended COSCUP(Conference for Open Source Coders, Users and
> Promotors) held in Taiwan. This year they are holding it with GNOME.Asia
> Summit.
>
> In a session they are talking about GNOME accessibility.  What confused me
> was
> that, different speakers in this session said that "there are no
> accessibility
> features and packages in KDE" (from a speaker who is a teacher in Taiwan),
> "The framework of KDE accessibility is not complete" (from speakers who
> work
> in Sun Oracle and are the GNOME accessibility developers).
>
> I remember that there are actually many features for KDE accessibility.  I
> translated them into our language.  Most, though not all, of the
> accessibility
> features they demoed should be in KDE as well.  However, they all seemed
> not
> to know or acknowledge the accessibility in KDE.  A listener even asked if
> they plan to port the framework of GNOME accessibility into KDE.
>

Franklin,

KDE Accessibility is nowhere near GNOME accessibility for completeness
unfortunately.  At least on linux.  There is a plan in place that has been
worked on by many to bridge qt accessibility to at-spi2 which is dbus based
rather than corba that at-spi used.  It's not quite ready yet though.  I
wrote a blog article about the state of kde accessibility a number of months
ago that can be read here:
http://jpwhiting.blogspot.com/2010/02/state-of-free-accessibility.html  Not
a whole lot has changed since then though.

Well, I don't mean to wage any war.  I'm just curious that, is the KDE
> accessibility features and framework THAT bad?  Or is it just because of
> being
> in the forum of GNOME?  What do you think about that?
>

Well, we have no support for screen-readers, or braille, or such.  We do
have magnification and some utilities for mouse help with disabilities, but
once qt-at-spi bridge is in place, kde/Qt apps should work with the gnome
screen reader Orca, and with any other gnome accessibility tools.

Regards,
Jeremy

>
>
> Franklin
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> unsubscribe <<
>

[Attachment #5 (text/html)]

<div class="gmail_quote">On Sat, Aug 14, 2010 at 8:42 AM, Franklin &lt;<a href="mailto:franklin@goodhorse.idv.tw">franklin@goodhorse.idv.tw</a>&gt; \
wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, \
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Hi list, 
 
Today I attended COSCUP(Conference for Open Source Coders, Users and 
Promotors) held in Taiwan. This year they are holding it with GNOME.Asia Summit. 
 
In a session they are talking about GNOME accessibility. What confused me was 
that, different speakers in this session said that &quot;there are no \
accessibility features and packages in KDE&quot; (from a speaker who is a teacher \
in Taiwan), &quot;The framework of KDE accessibility is not complete&quot; (from \
speakers who work in Sun Oracle and are the GNOME accessibility developers). 
 
I remember that there are actually many features for KDE accessibility. I 
translated them into our language. Most, though not all, of the accessibility 
features they demoed should be in KDE as well. However, they all seemed not 
to know or acknowledge the accessibility in KDE. A listener even asked if 
they plan to port the framework of GNOME accessibility into \
KDE. </blockquote><div> Franklin, KDE Accessibility is nowhere near \
GNOME accessibility for completeness unfortunately. At least on linux. There is a \
plan in place that has been worked on by many to bridge qt accessibility to at-spi2 \
which is dbus based rather than corba that at-spi used. It&#39;s not quite ready yet \
though. I wrote a blog article about the state of kde accessibility a number of \
months ago that can be read here: <a \
href="http://jpwhiting.blogspot.com/2010/02/state-of-free-accessibility.html">http://jpwhiting.blogspot.com/2010/02/state-of-free-accessibility.html</a> \
Not a whole lot has changed since then though. </div><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"> Well, I don&#39;t mean to wage any war. I&#39;m just \
curious that, is the KDE accessibility features and framework THAT bad? Or is it \
just because of being in the forum of GNOME? What do you think about \
that? </blockquote><div> Well, we have no support for screen-readers, or \
braille, or such. We do have magnification and some utilities for mouse help with \
disabilities, but once qt-at-spi bridge is in place, kde/Qt apps should work with the \
gnome screen reader Orca, and with any other gnome accessibility tools. \
 Regards, Jeremy </div><blockquote class="gmail_quote" \
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; \
padding-left: 1ex;"> 
 
Franklin 
 
&gt;&gt; Visit <a href="http://mail.kde.org/mailman/listinfo/kde-devel#unsub" \
target="_blank">http://mail.kde.org/mailman/listinfo/kde-devel#unsub</a> to \
unsubscribe &lt;&lt; </blockquote></div>

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread] 