Hi Rekha,
My apologies for taking so long to get back to you. Your message got caught up in moderation and then I missed it afterwards.
Since Web Consistency Testing effectively works with a snapshot of the DOM, Ajax pages shouldn't present any real problem for the detection engine. Now, if you're using a third-party service or building your own tool, they'll have to account for that. Two solutions I've used in the past are:
1) Use hash fragments in your URLs to indicate the state you're testing (optionally having a test script key off the fragment in order to drive the page to that state).
2) Use a tool like Selenium to perform the actions you need in order to get the page in the appropriate state and then use your DOM capture tool.
Hopefully that answers your question. Web Consistency Testing was designed with rich applications in mind, so it should handle this okay.