Talk:Accessibility Toolkit
![]() | Accessibility Toolkit received a peer review by Wikipedia editors, which is now archived. It may contain ideas you can use to improve this article. |
![]() | This article is rated Stub-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||||||||||
|
Not GNOME
[edit]They way I understand it, ATK is not directly related to GNOME in any way. It's a package that can be installed along with GTK+, to extend it. Just like GTK+, ATK is usable (and in fact often used) independently of GNOME. That's the same common mistake as to say that GTK+ is the GNOME toolkit. It's not. GNOME merely uses it, although quite heavily. 85.1.179.10 11:31, 21 January 2007 (UTC)
Rationale for adding download link
[edit]I don't know about others, but I have a (potentially questionable) habit of looking up various open source products on Wikipedia and from there go to a site where I conveniently can download the software. This page contains a link to the project page (or at least something which seem to have some high level relation with ATK) but from there it were difficult to find any link leading to sites with actual software downloads. So, I decided to add an external link to the article itself that is aiming directly to the place where one could download ATK. Feel free to improve as you see fit. IllvilJa (talk) 17:33, 17 May 2010 (UTC)
I would like to update this article
[edit]I would like to change the current content in order to provide updated and more accurate information. How I have to proceed ?
The main sources for the new content are:
- Accessibility in WebKitGTK+
- ATK Developer Documentation
- GNOME Committed to Accessibility
- GNOME 3.2 Release Notes
- GNOME 3.6 Release Notes: Accessibility Always On
TIA, Jjmarin (talk) 23:02, 6 February 2013 (UTC)
New content proposal
[edit]In computing, Accessibility Toolkit (ATK) refers in particular to the GNOME ATK.
ATK is a specification created by the GNOME Project to enable accessibility for users needing extra support to make the most of their computers. ATK defines interfaces that exposes accessible representations of the toolkit’s graphic objects on the side of the applications. This representation is an almost a 1:1 match with the objects and interfaces defined by AT-SPI. The main difference between both representations is that ATK is process-bounded so the parent/children relationships in the ATK hierarchy are modelled by actual references (pointers) between objects living in the same process.[1]
Implementations
[edit]The ATK abstract headers are freely available[2] to help developers who want to make their toolkits accessible. Developers who use stock widgets of 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 worry about exposing accessible information.
GAIL (GNOME Accessibility Implementation Library) is the implementation of the accessibility interfaces 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 has been merged into GTK+.[3]
Apart from GTK+, other graphical toolkits has implemented ATK in order to be accessible like Java Swing[4] and SWT[5] , OpenOffice[6] /LibreOffice[7] , Mozilla’s Gecko[8] , Clutter[9] and WebKitGTK+[1].
History
[edit]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) 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 like the Accessibility Toolkit ATK and the Orca screen reader. Since then, ATK is mainly running by volunteers, lead by Alejandro Piñeiro[11].
Licensing
[edit]ATK is released under the GNU Library General Public License (LGPL) version 2.
See also
[edit]- Microsoft_Active_Accessibility – Microsoft Active Accessibility (MSAA)
- Microsoft_UI_Automation – Microsoft UI Automation (UIA)
- IAccessible2
References
[edit]- ^ a b Sánchez Prada, Mario. "Accessibility in (WebKit)GTK+". Retrieved 19 February 2013.
- ^ "ATK abstract headers".
- ^ "GNOME 3.2 Release Notes". Retrieved 19 February 2013.
- ^ "Java Access Bridge". Retrieved 24 February 2013.
- ^ "Eclipse 3.0 - New and Noteworthy in SWT". Retrieved 24 February 2013.
- ^ "OpenOffice ATK wrapper code". Retrieved 24 February 2013.
- ^ "LibreOffice ATK wrapper code". Retrieved 24 February 2013.
- ^ "Mozilla Accessibility Architecture". Retrieved 24 February 2013.
- ^ "Cally web page at GNOME". Retrieved 19 February 2013.
- ^ "Making GNOME Accessible -- Opening New Doors At the Workplace for Users with Disabilities". GNOME Foundation. Retrieved 25 February 2013.
- ^ Willis, Nathan (December 21, 2011). "GNOME plans an accessibility push for 2012". Linux Weekly News. Retrieved 24 February 2013.
Jjmarin (talk) 07:27, 25 February 2013 (UTC)
Poor: "See Also" Section
[edit]I will give this wiki article bad note.
I mean especially See also section.
I am ordinary PC (Linux) user, and I would like to find out quickly through wiki site how to turn on Sounds during typing on Keyboard.
I need that for languages:
Hebrew, Arabic, Hindi, Chinese & Japanese.
And See Also section does not help we with that!!! — Preceding unsigned comment added by 46.187.193.238 (talk) 20:24, 3 April 2021 (UTC)