Screening Out Unnecessary Objects

If you use either of the Active Accessibility SDK tools Inspect Objects or Accessible Explorer to examine a simple control such as an OK push button in the WordPad accessory, you can see that these parent window objects also contain several invisible child objects. These invisible objects have the same window class name as the control and have the State property of STATE_SYSTEM_INVISIBLE. The following table lists the invisible child objects that Active Accessibility creates for the control.

Name Role ChildCount
"System" ROLE_SYSTEM_MENUBAR 0
None ROLE_SYSTEM_TITLEBAR 5
"Application" ROLE_SYSTEM_MENUBAR 0
"Vertical" ROLE_SYSTEM_SCROLLBAR 5
"Horizontal" ROLE_SYSTEM_SCROLLBAR 5
"Size Box" ROLE_SYSTEM_GRIP 0

Client developers must identify and filter out these parent window objects and invisible child objects because they do not provide meaningful information to end users.