Editing Computer accessibility (section)

== Open Accessibility Framework ==

The Open Accessibility Framework (OAF)<ref>AEGIS Consortium: [http://www.aegis-project.eu/images/docs/AEGIS_D1.2.1_final-revised_2nd_Annual_Review.pdf AEGIS OAF and high-level architecture]. Accessed 2013-01-17.</ref> provides an outline of the steps that must be in place in order for any [[computing platform]] to be considered accessible. These steps are analogous to those necessary to make a physical or built environment accessible. The OAF divides the required steps into two categories: creation and use.

The "creation" steps describe the precursors and building blocks required for technology developers to create accessible applications and products. They are as follows:
# Define what "accessible" means for the identified use of the platform.  It must be clear what is meant by "accessible" as this will differ according to the [[modality (human-computer interaction)|modality]] and capabilities of each platform. Accessibility features may include [[tabbing navigation]], [[Theme (computing)|theming]], and an [[Screen reader#Accessibility APIs|accessibility API]].
# Provide accessible stock [[Elements of graphical user interfaces|user interface elements]]. Pre-built "stock" user interface elements, used by application developers and authoring tools, must be implemented to make use of the accessibility features of a platform.
# Provide authoring tools that support accessibility. Application developers and content authors should be encouraged to implement tools that will improve the accessibility features of a platform. Using these tools can support accessible stock user interface elements, prompt for information required to properly implement an accessibility API, and identify accessibility evaluation and repair tools.

The "use" steps describe what is necessary for the computing environment in which these accessible applications will run. They are as follows:
# Provide platform supports. Computing platforms must properly implement the accessibility features that are specified in their accessibility definition. For example, the accessibility API definitions must be implemented correctly in the program code.
# Provide accessible [[Computer applications|application software]]. Accessible applications must be available for the platform and they must support the accessibility features of the platform. This may be achieved by simply engaging the accessible stock elements and authoring tools that support accessibility.
# Provide [[assistive technologies]]. Assistive technologies (e.g. screen readers, screen magnifiers, voice input, adapted keyboards) must actually be available for the platform so that the users can effectively interface with the technology.

The following examples show that the OAF can be applied to different types of platforms: desktop operating systems, web applications<ref>AEGIS Consortium: [http://www.aegis-project.eu/images/docs/ApprovedDeliverablesForWebsite/AEGIS_D3.1.2_final.pdf AEGIS Architecture Definition]. Accessed 2013-01-17.</ref> and the mobile platform. A more complete list can be found in the Open Source Accessibility Repository by the Open Accessibility Everywhere Group (OAEG).

# 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>[http://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.
# The [[GNOME Shell]] Magnifier and [[Orca (assistive technology)|Orca]] on the GNOME desktop, GNOME's [[Accessibility Toolkit|ATK]] (Accessibility Toolkit), the web-based screen reader [[WebAnywhere]],<ref>WebInSight: [http://webanywhere.cs.washington.edu/ WebAnywhere: A Screen reader on the go] {{webarchive|url=http://arquivo.pt/wayback/20160523013006/http://webanywhere.cs.washington.edu/ |date=2016-05-23 }}. Accessed 2013-01-17.</ref> and the alternative text-entry system [[Dasher (software)|Dasher]] for [[Linux]], iOS and Android<ref>Inference Group (University of Cambridge): [http://www.inference.phy.cam.ac.uk/dasher/MobileDasher.html Mobile Dasher]. Accessed 2013-01-17.</ref><ref>[https://web.archive.org/web/20100729145114/http://itunes.apple.com/us/app/dasher/id315473092?mt=8 Dasher for iOS] on iTunes. Accessed 2013-01-17.</ref> are examples of assistive technologies.

The goal of the listed tools is to embed accessibility into various mainstream technologies.<ref>Iosif Klironomos, Julio Abascal, Ilse Bierhoff: [http://www.cardiac-eu.org/deliverables/d3-1.htm D3.1 Report with background material needed to support the SDDP-2 Meeting: An Introduction to the Key Issues Relating to Accessible User Interfaces]. Accessed 2013-01-17.</ref>