Use acccheck with webpages

Apr 17, 2009 at 10:44 PM
It is possible to check the accessibility of webpages using acccheck api

Apr 23, 2009 at 6:24 PM

Hi Eric,

The short answer is "No, you cannot use AccChecker to test webpages."

The long answer:

The currently published latest version (v1.1) of AccChecker does not include verifications suitable for webpages.  You could run the current verifications on a webpage, however the results may not be very relevant, since web browsers expose MSAA differently compared to standard Windows user interfaces.  Also, the APIs expose the same verifications that are available through the GUI and Console mode, so that limitation will be available in all 3 modes (GUI, console, APIs).

Certain verifications could make sense for webpages (such as parent-child relationship), however they would be testing much more the accessibility of the rendering engine (Trident for Internet Explorer or Gecko for Firefox), rather than the accessibility of the webpage itself.

While we don't have a plan of record, we expect that future versions of AccChecker will include webpage verifications, so stay tuned.  Hope this helps.

Best regards,
Peter Lakov
AccChecker Program Manager

Aug 23, 2009 at 6:12 AM

Hi Peter!

I have already started a discussion in UIVerify discussions on the subject...

As per this post, I could not find UI elements placed on an HTML page that is embedded in a windows container which is part of a windows application, using UIVerify. When I used AccChecker to verify the same, I'm able to find all the controls in the said html page in a tree view and could visualize them as well. For example, there is a link, which is found in the tree as follows...

Name: Deposit

Value: javascript:openCashierDeposit()

Role: Text

State: Linked ReadOnly Selectable Focusable

Location: {X=983,Y=203,Width=44,Height=12}

My request now to you is that, how would get this object so that I can programmatically perform an actions such as verification of name or most importantly clicking the link.






Sep 3, 2009 at 1:45 AM


Are you asking how to select an individual control with AccChecker and run the verifications on that control (rather than on an entire window)?

AccChecker was designed to specify entire windows (on a HWND boundary) on which to run the verifications – the current version doesn’t have the granularity to specify individual controls.  For that, you may need to use some other tools, such as Inspect (they don’t have the verifications, but you can use them to select and view individual controls.

Also, if you need to run the verifications on individual controls, could you explain what the value of doing that is?  It seems that for the UI as a whole to work correctly, all the controls should be well accessible, not just a few.