Organizations are beginning to give a lot of attention and importance to accessibility engineering as part of their usability efforts; however, this has not translated into implementation strategies that have reached the market. Why is there a reluctance to venture into full-fledged accessibility engineering?

When we design, build, test, and deliver software, it is imperative that we provide our users with what they need—not what we want, but what that they want. We need to understand the scope and breadth of the user base. Here are three questions to ask to learn more about how users experience your software.

Pair programming generally involves two programmers working on a single change from start to finish. You can augment this pattern by adding a test specialist, so you can test-drive feature changes first and the tester can ask questions and guide test and code design. What you get is quality built in from the start.