Computer accessibility: Difference between revisions

Revision as of 14:28, 21 June 2025

Revision as of 18:30, 9 August 2025

Line 131:

# Accessibility APIs include the [[Assistive Technology Service Provider Interface]] and [[UI Automation]] on the desktop, [[WAI-ARIA]] in web applications, and the Blackberry Accessibility API<ref>Research in Motion (RIM): [http://www.blackberry.com/developers/docs/6.0.0api/net/rim/device/api/ui/accessibility/package-summary.html Package net.rim.device.api.ui.accessibility]. BlackBerry JDE 6.0.0 API Reference. Accessed 2013-01-17.</ref> on the Blackberry operating system.

# Other APIs are keyboard access and theming in widget libraries like [[Java Swing]] for desktop applications, the [[jQuery UI]] and Fluid Infusion<ref>[http://fluidproject.org/products/infusion Fluid Infusion]. Accessed 2013-01-17.</ref> for Web applications, and the [[Lightweight User Interface Toolkit]] (LWUIT) for mobile applications.

# Support for accessible development can be effective by using [[Glade Interface Designer|Glade]] (for the GTK+ toolkit),<ref>[httphttps://glade.gnome.org/ Glade - A User Interface Designer]. Accessed 2013-01-17.</ref> the DIAS plugin for NetBeans IDE,<ref>[http://sourceforge.net/projects/diasnb/ DIAS Netbeans IDE plugin & Standalone]. Accessed 2013-01-17.</ref> [[Xcode]] IDE for [[iOS]] applications.<ref>Apple Inc.: [https://developer.apple.com/xcode/ Xcode 4]. Accessed 2013-01-17.</ref> Accessibility inspection tools like Accerciser (for [[Assistive Technology Service Provider Interface|AT-SPI]])<ref>[https://live.gnome.org/Accerciser Accerciser].</ref> and support for accessible authoring with the AccessODF plugin for [[LibreOffice]] and [[Apache OpenOffice]]<ref>[http://accessodf.sourceforge.net/index.html#oaf AccessODF]. Accessed 2013-01-17.</ref> also fit into this step.

# Support for UI Automation on Microsoft Windows,<ref name=":3">Microsoft Developer Network: [http://msdn.microsoft.com/en-us/library/ms753388.aspx Accessibility (.NET Framework 4.5)]. Accessed 2013-01-17.</ref><ref>Microsoft Windows Dev Center: [http://msdn.microsoft.com/en-us/library/windows/desktop/ee684009.aspx UI Automation (Windows)]. Accessed 2013-01-17.</ref> support for ATK and AT-SPI in Linux GNOME,<ref>GNOME Dev Center: [http://developer.gnome.org/accessibility-devel-guide/3.0/dev-start-5.html.en Introducing ATK, AT-SPI, GAIL and GTK+]. Accessed 2013-01-17.</ref> WAI-ARIA support in Firefox,<ref>[https://www.mozilla.org/access/ Access Mozilla]. Accessed 2013-01-17.</ref><ref>Access Firefox: [http://www.accessfirefox.org/Firefox_Accessibility_Features Firefox Accessibility Features]. Accessed 2013-01-17.</ref> and the MIDP LWUIT mobile runtime<ref>AEGIS Consortium: [http://www.aegis-project.eu/index.php?option=com_content&task=view&id=155&Itemid=24 LWUIT - Mobile Accessibility]. Accessed 2013-01-21.</ref> (or the MIDP LCDUI mobile runtime) that is available on mobile phones with Java are examples of APIs.

# The [[DAISY Digital Talking Book|DAISY]] player AMIS on the Microsoft Windows desktop<ref>DAISY Consortium: [http://www.daisy.org/amis/amis-daisy-2.02-daisy-3-playback-software AMIS: DAISY 2.02 & DAISY 3 Playback Software]. Accessed 2013-01-17.</ref> and the AEGIS Contact Manager for phones with Java ME<ref>[http://store.ovi.com/content/212755?clickSource=search&pos=1 AEGIS Contact Manager]. Accessed 2013-01-17.</ref> are designed for accessibility.