 | This article has multiple issues. Please helpimprove it or discuss these issues on thetalk page.(Learn how and when to remove these messages) (Learn how and when to remove this message)
|
| ATK | |
|---|---|
 | |
| Stable release | |
| Repository | |
| License | GNU LGPL (version 2)[2] |
| Website | wiki |
Accessibility Toolkit (ATK) is an open sourcesoftware library, part of theGNOME project, which providesapplication programming interfaces (APIs) for implementingaccessibility support in software.
One common nomenclature to explain an accessibility framework is a usualclient-server architecture. In that way,assistive technologies (ATs) such asscreen readers, would be the clients of that framework, and computer applications would be the server. In this architecture the client and server need to communicate with each other, usually using theIPC technology of the platform. Ideally the accessibility framework expose this to the client and server in a transparent way.
Usually the API for both client-side and server-side applications are the same, and the accessibility framework provides a client-side and a server-side implementation of that API. In the case of GNOME, there are two different APIs, one for the client-side (Assistive Technology Service Provider Interface (AT-SPI)) and a different one for the server-side (ATK) due to historical reasons related to the underlying technologies.[3]
The ATK abstractheaders files are freely available to help developers who want to make theirGUI toolkit accessible.[4] Developers who use stockwidgets of GUI toolkits that implements the ATK headers can more easily make their applications accessible. However, if they develop their own widgets, they will have to ensure that they are exposing all the accessible information.
GAIL (GNOME Accessibility Implementation Library) was the name of the accessibility interfaces implementation defined by ATK forGTK+, the widget library of GNOME. Initially, GAIL was an independent module mapped to GTK+ but since GNOME 3.2, GAIL was merged into GTK+, so the ATK implementation is integrated into GTK+ and GAIL is deprecated.[5]
Apart from GTK+, other GUI toolkits and applications have implemented ATK in order to be accessible, such as OpenOffice[6]/LibreOffice,[7] Mozilla's Gecko,[8] Clutter[9] and WebKitGTK+.[3]
ATK is part of the GNOME Accessibility Framework that was released in 2001.[10] The main development force behind ATK was the Accessibility Program Office (APO) ofSun Microsystems, Inc. (nowOracle) with contributions from many community members. When Oracle acquired Sun in 2010 they cut developer jobs of full-time developers working on GNOME accessibility components such as the Accessibility Toolkit ATK and the Orca screen reader.[11] Since then, ATK is mainly maintained by the GNOME community.
DuringGUADEC 2020 Emanuelle Bassi announced to have been working for about 6 months on a successor to ATK.[12] Accessibility will no longer be maintained out-of-tree but be part ofGTK. Available since GTK 3.99.0[13] The new approach will implement WAI-ARIA (World Wide Web Consortium (W3C) Accessibility Initiative – Accessible Rich Internet Applications).
ATK development has been led by their maintainers with the help of its community. The maintainers so far are:[14]
Current:
Previous:
| Core Applications | |||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Extras |
| ||||||||||||||||
| Components |
| ||||||||||||||||
| Community | |||||||||||||||||
| People | |||||||||||||||||
