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

List:       kde-core-devel
Subject:    Re: [Kde-accessibility] focus tracking
From:       Jeremy Whiting <jpwhiting () kde ! org>
Date:       2010-06-29 16:47:52
Message-ID: AANLkTikW2jJbArwb7C7U02a07ekkWUrjxQQixKgLvSwT () mail ! gmail ! com
[Download RAW message or body]

Adding gnome-accessibility and accessibility to the lists as they are the
ones with the answers in this regard I believe.

Joanie, we are discussing magnification, and I thought you'd likely know the
answer about the api orca/gnome mag uses that Gunnar mentioned here.

Jeremy (connecting the right people since 2009)

2010/6/29 Aaron J. Seigo <aseigo@kde.org>

> (... removing the e.v. membership list, because technical discussion does
> not
> belong there ...)
>
> On June 28, 2010, Gunnar Schmidt wrote:
> > individual user applications, and a special magnification API is used for
> > the communication between a screen reader and the magnifier (so that the
> > screen magnifier does itself not need an AT-SPI implementation.
>
> do you know if the magnification API is going to be kept with / ported to
> AT-
> SPI2? if so, then it would be possible to make use of that API with the
> kwin
> magnification desktop effect (when used as an a11y aid) and when AT-SPI2
> becomes available, nothing in kwin's code would need to change. but that
> relies on the magnification API remaining stable ... (which i hope it
> would,
> for the sake of other magnifiers out there)
>
> --
> Aaron J. Seigo
> humru othro a kohnu se
> GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43
>
> KDE core developer sponsored by Qt Development Frameworks
>
> _______________________________________________
> kde-accessibility mailing list
> kde-accessibility@kde.org
> https://mail.kde.org/mailman/listinfo/kde-accessibility
>
>

[Attachment #3 (text/html)]

Adding gnome-accessibility and accessibility to the lists as they are the ones with \
the answers in this regard I believe.<br><br>Joanie, we are discussing magnification, \
and I thought you&#39;d likely know the answer about the api orca/gnome mag uses that \
Gunnar mentioned here.<br> <br>Jeremy (connecting the right people since \
2009)<br><br><div class="gmail_quote">2010/6/29 Aaron J. Seigo <span dir="ltr">&lt;<a \
href="mailto:aseigo@kde.org">aseigo@kde.org</a>&gt;</span><br><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"> (... removing the e.v. membership list, because \
technical discussion does not<br> belong there ...)<br>
<div class="im"><br>
On June 28, 2010, Gunnar Schmidt wrote:<br>
&gt; individual user applications, and a special magnification API is used for<br>
&gt; the communication between a screen reader and the magnifier (so that the<br>
&gt; screen magnifier does itself not need an AT-SPI implementation.<br>
<br>
</div>do you know if the magnification API is going to be kept with / ported to \
AT-<br> SPI2? if so, then it would be possible to make use of that API with the \
kwin<br> magnification desktop effect (when used as an a11y aid) and when AT-SPI2<br>
becomes available, nothing in kwin&#39;s code would need to change. but that<br>
relies on the magnification API remaining stable ... (which i hope it would,<br>
for the sake of other magnifiers out there)<br>
<div><div></div><div class="h5"><br>
--<br>
Aaron J. Seigo<br>
humru othro a kohnu se<br>
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43<br>
<br>
KDE core developer sponsored by Qt Development Frameworks<br>
</div></div><br>_______________________________________________<br>
kde-accessibility mailing list<br>
<a href="mailto:kde-accessibility@kde.org">kde-accessibility@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-accessibility" \
target="_blank">https://mail.kde.org/mailman/listinfo/kde-accessibility</a><br> \
<br></blockquote></div><br>



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