This article may be too technical for most readers to understand.December 2018) (Learn how and when to remove this template message)(
2.28.1 / March 13, 2018
|License||GNU LGPL (version 2)|
One common nomenclature to explain an accessibility framework is a usual client-server architecture. In that way, assistive technologies (ATs) such as screen 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 the IPC 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.
The ATK abstract headers files are freely available to help developers who want to make their GUI toolkit accessible. Developers who use stock widgets of GUI toolkits that implements the ATK headers don't have to worry too much for making 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 for GTK+, 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.
ATK is part of the GNOME Accessibility Framework that was released in 2001. The main development force behind ATK was the Accessibility Program Office (APO) of Sun Microsystems, Inc. (now Oracle) 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. Since then, ATK is mainly maintained by the GNOME community.
During GUADEC 2020 Emanuelle Bassi announced to have been working for about 6 months on a successor to ATK. Accessibility will no longer be maintained out-of-tree but be part of GTK. Available since GTK 3.99.0 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:
- Alejandro Piñeiro Iglesias
- Bill Haneman
- Leon Fan
- Li Yuan
- "index : atk". Retrieved 11 April 2017.
- "ATK git source code repository, COPYING file". Retrieved 2014-03-30.
- Sánchez Prada, Mario (February 3, 2013). "Accessibility in [WebKit]GTK+". Retrieved 2014-03-30.
- "ATK source code". Retrieved 2014-03-30.
- "GNOME 3.2 release notes". Retrieved 2014-03-30.
- "Apache OpenOffice ATK implementation source code". Retrieved 2014-03-30.
- "LibreOffice ATK implementation source code". Archived from the original on 2014-05-18. Retrieved 2014-03-30.
- "Mozilla accessibility architecture". Retrieved 2014-03-30.
- "Cally (Clutter Accessibility Implementation Library) project page". Retrieved 2014-03-30.
- "Making GNOME Accessible -- Opening New Doors At the Workplace for Users with Disabilities". GNOME Foundation. Retrieved 2014-03-30.
- Walker, Willie (March 30, 2010). "GNOME Accessibility Hackfest". Retrieved 2014-03-30.
- "GUADEC 2020 slide decks".
- "Release of gtk 3.99.0".
- "ATK's Maintainers file". Retrieved 2014-03-30.