Ramesh,
This is of great interest to me as well.
I have run into the challenge of having a 508 testing team essentially say "see saw a lot of problems with ADF" without having fully identified the isssues.
Clearly, Oracle has had to (and indeed has) spent considerable resources ensure ADF can meet current 508 requirements (I also hear there is a new round of requirements coming down)
What are looking to do is to develop a set of patterns, guidelines and templates to ensure the highest probability of compliance at the design and development stage -- waiting until testing (and delaying testing until late in the cycle) ensures that remediation and corrections are far more burdensome.
We do not have these guidelines in place -- I would like to vet them and otherwise share them with this group when we do.
In the meantime, I would appreciate any specific input and love to see an active thread about this. Some basics:
-- The biggest factor I have seen is that there out is great support for 508 compliance in ADF *but* it requires you complete necessary metadata at design/development time (e.g., not in testing)
I look forward to further dialogue on this topic!
Nathaniel Palmer