Selenium is good for conventional web testing. But when accessibility is factored in, we discover a whole new QA nightmare.
How do we keep our web application's quality and accessibility consistent across browsers, platforms and assistive technologies?
And speaking of “conventional” testing, how do we make accessibility QA part of the “conventional” test suite?
It is hard to provide good QA coverage for so many an unlimited set of assisitive technologies. But Windows accessibility APIs are a different story.