It is important to remember that, although written in JavaTM, Eclipse applications follow the accessibility API of the target desktop operating system. Eclipse provides a rich plug-in environment whereby the norm is to create plug-ins for native widgets. Most of the SWT widgets that come with Eclipse are actually JavaTM wrappers for native GUI widgets. (This is the complete opposite of a pure JavaTM GUI written in Swing in which higher level components do not translate to native operating system widgets.) When a widget does not exist on all platforms, it is emulated in code on the deficient platform. Therefore SWT Widgets utilize accessibility features of the underlying operating system widgets when available, and provide accessibility using MSAA and IAccessible2 in emulated widgets.
The first of three components is the application (or plug-in) which is built using SWT. This component is platform independent because SWT isolates the application from the platform. The org.eclipse.swt.accessibility package runtime provides the bridge from the application to the platform. The second component is the platform accessibility framework, such as Windows® MSAA or GNOMETM GAP. The third component is the assistive technology, such as the JAWS screen reader. At runtime, the AT obtains information about the user interface elements by calling the platform accessibility framework, which in turn calls into the .swt.accessibilitypackage.
SWT.COLOR_YELLOW is the example of SWT color. Similarly JFaceResources.getBannerFont is the font provided by JFACE
Clabel is used with Ccombo. Had we used Combo, Label should be used.
Here master group is added and there are two editors inside master group, user Editor and password editor. Example taken from RPE Remote services preferences.
Group is a composite which does not take focus. We need to setFocus explicitly for such components to be accessible.
AccessibleActionListener - Classes which implement this interface provide methods that handle AccessibleAction events.
AccessibleAttributeListener - Classes which implement this interface provide methods that handle AccessibleAttribute events.
AccessibleListener - Classes that implement this interface provide methods that deal with the events that are generated when an accessibility client sends a message to a control.
AccessibleAdapter - This adapter class provides default implementations for the methods described by the AccessibleListener interface.
AccessibleEvent - Instances of this class are sent as a result of accessibility clients sending messages to controls asking for information about the control instance