keropmix.blogg.se

Microsoft accessibility standards
Microsoft accessibility standards




  1. #Microsoft accessibility standards software#
  2. #Microsoft accessibility standards windows 7#
  3. #Microsoft accessibility standards professional#
  4. #Microsoft accessibility standards windows#

Accessibility tools (e.g., screen readers) are called Clients in MSAA because they consume and interact with UI information from an application. COM defines a mechanism for applications and operating systems to communicate.įigure 1 shows a high-level architecture of MSAA.Īpplications (e.g., word processor) are called Servers in MSAA because they provide, or serve, information about their user interfaces (UI). MSAA is based on the Component Object Model (COM).

#Microsoft accessibility standards windows#

The programmatic goal of MSAA is to allow Windows controls to expose basic information, such as name, location on screen, or type of control, and state information such as visibility, enabled, or selected. The motivating factor behind the development of MSAA was to allow an available and seamless communication mechanism between the underlying operating system or applications and assistive technology products.

#Microsoft accessibility standards windows 7#

Windows Automation API is included in Windows 7 and available for Windows Vista and XP (2009) The framework has become part of the Windows Automation API 3.0, which is integrated into the Windows platform accessibility API set by MSAA and UI Automation (UIA). The 2.0 version of the RDK was made available to older platforms (Windows 95, 98, 2000, Me, NT) in 2003. Minor revisions have been made to the MSAA framework within subsequent versions of Windows. This version was integrated into Windows XP. (1999)įirst major revision of MSAA, adding support for Dynamic Annotation and MSAA Text. Later the system components were integrated into Windows NT 4.0 Service Pack 6 and beyond, Windows 98, Windows 2000 and Windows Me. Introduced satellite DLL (oleaccrc.dll) for its international text resource library. (1998)Īdditional support added for more languages. (1997)įirst revision of MSAA that was made available to both English and international versions of Windows. The RDK was supported only in the English version of the operating system. The following Active Accessibility versions have been released: Version However, newer applications are now using Microsoft UI Automation (UIA), which was introduced in Windows Vista and the. Programmatic exposure for assistive technology applications on Windows has historically been provided through MSAA. Since Windows 98 and Windows NT 4.0 Service Pack 4, MSAA has been built-into all versions of the Windows platform, and has received periodic upgrades and patches over time. The RDK included updated operating system components for Microsoft Windows 95. The SDK packaged included documentation, programming libraries, sample source code, and a Re-Distributable Kit (RDK) for accessible technology vendors to include with their products.

#Microsoft accessibility standards software#

MSAA was originally made available in April 1997 as part of the Microsoft Active Accessibility Software Developers Kit (SDK) version 1.0. Later, the ActiveX branding was reserved for internet-specific technologies, and ActiveX Accessibility became Active Accessibility and frequently shortened to MSAA.

#Microsoft accessibility standards professional#

As part of Microsoft's ActiveX branding push in March 1996, OLE Accessibility was renamed ActiveX Accessibility (sometimes referred to as AXA) and presented as such at the Microsoft Professional Developers Conference in San Francisco, March 1996.

  • 10 Implementations of Microsoft Active AccessibilityĪctive Accessibility was initially referred to as OLE Accessibility and this heritage is reflected in the naming of its binary components such as oleacc.dll and the header file oleacc.h which contains definitions and declarations.
  • microsoft accessibility standards

    The current and latest specification of MSAA is found in part of Microsoft UI Automation Community Promise Specification. MSAA can also be used for automated testing tools, and computer-based training applications. Some examples of AT products are screen readers for users with limited sight, on screen keyboards for users with limited physical access, or narrators for users with limited hearing. AT products work with MSAA enabled applications in order to provide better access for individuals who have physical or cognitive difficulties, impairments, or disabilities. MSAA is designed to help Assistive Technology (AT) products interact with standard and custom user interface (UI) elements of an application (or the operating system), as well as to access, identify, and manipulate an application's UI elements. MSAA was introduced as a platform add-on to Microsoft Windows 95 in 1997. Microsoft Active Accessibility ( MSAA) is an application programming interface (API) for user interface accessibility.






    Microsoft accessibility standards