Bug 144590 [Accessibility] BIRT custom controls should support active accessibility
Description: BIRT custom controls should support active accessibility. There are some custom controls in BIRT GUI. In Eclipse, when implementing a custom control you should also implement some or all of (as they apply to your control) org.eclipse.swt.accessibility.AccessibleListener, org.eclipse.swt.accessibility.AccessibleControlListener and org.eclipse.swt.accessibility.AccessibleTextListener. Also, the custom control can notify Active Accessibility of changes within the control using org.eclipse.swt.accessibility.Accessible methods such as setFocus(), selectionChanged(), textCaretMoved(), textChanged() and textSelectionChanged().
UI/org.eclipse.birt.report.designer.ui.editors/src/org/eclipse/birt/report/designer/ui/editors/MultiPageReportEditor.java
/**
 * 
 * Base multipage editor for report editors. Clients can subclass this class to
 * create customize report editors. Report editor pages can contributed through
 * Extendtion Point
 * org.eclipse.birt.report.designer.ui.editors.multiPageEditorContributor.
 * 
 * @see IReportEditorPage
 */
public class MultiPageReportEditor extends AbstractMultiPageEditor
		implements
			IPartListener,
			IReportEditor,
			IColleague
{
	public static final String LayoutMasterPage_ID = "org.eclipse.birt.report.designer.ui.editors.masterpage";
	public static final String LayoutEditor_ID = "org.eclipse.birt.report.designer.ui.editors.layout";
	private ReportMultiBookPage fPalettePage;
	private ReportMultiBookPage outlinePage;
	private ReportMultiBookPage dataPage;
	private boolean fIsHandlingActivation;
	private long fModificationStamp = -1;;
	protected IReportProvider reportProvider;
	
	
	
	
	private static class FormEditorSelectionProvider
			extends
				MultiPageSelectionProvider