libqaccessibilityclient now in kdereview
bcooksley at kde.org
Wed Jul 26 07:11:18 BST 2017
On Wed, Jul 26, 2017 at 9:18 AM, Mario Fux <kde-ml at unormal.org> wrote:
> Am Dienstag, 25. Juli 2017, 14:55:42 CEST schrieb Albert Astals Cid:
> Morning Albert
>> El dimarts, 25 de juliol de 2017, a les 13:25:39 CEST, Jonathan Riddell va
>> > libqaccessibilityclient is now in kdereview. It's in a git repo
>> > called libkdeaccessibilityclient but we filed a sysadmin request to
>> > rename it.
>> > We just released 0.2.0 in unstable (for some reason 0.1.1 was released
>> > in stable some years ago).
>> Do we really have to keep the Qt4 compatibility or can we kill it?
> Please keep it for now as the next Simon release (0.5.0 which is on its way)
> is still Qt4 based.
Simon is (for the moment at least) prohibited from depending on
libqaccessibilityclient, because Extragear (as well as Plasma and
Applications module) applications are not allowed to depend on code
which is in Playground or KDE Review.
>> > What is it?
>> > ========
>> > Since it's hard to grasp all the bits related to accessibility, I'll try
>> > to
>> > explain what the lib is for.
>> > Most of the stack is part of Qt 5, so nothing to worry about, that's the
>> > part that lets applications expose their UI over DBus for AT-SPI, so they
>> > work nicely with assisitve tools (e.g. Orca). In accessibility language,
>> > the applications act as "servers" and the screen reader for example is a
>> > client.
>> > This library is for writing clients, so applications that are assistive,
>> > such as screen readers. It currently has two users: KMag and Simon.
>> > KMag can use it to follow the focus (e.g. when editing text, it can
>> > automatically magnify the part of the document where the cursor is.
>> > For Simon Listens, the use is to be able to let the user trigger menus and
>> > buttons by voice input.
More information about the kde-core-devel