In large organisations, a lot of focus can be put on enhancements. The customer needs to stay on our pages longer! More feedback forms need to be filled! We need more newsletter-subscriptions!

Everything is focussed on conversion rates. More customers. More sales. More money. Optimize until you’ve got the sleekest and best-selling journey for your customers. (And make sure to do it cheap)

Forget about optimization. You need to do accessibility first.

When there’s an accessibility issue, you’re excluding people. It doesn’t mean a group of people doesn’t buy as much as you’d like. It means a group of people can’t buy at all. They’re not a tad slow in completing your customer journey. They can’t even finish your customer journey.

Optimization is about being best in class. It’s about being the best option for people. But if you have accessibility issues, then you’re not even an option to begin with. People do not choose a competitor over you. They have no choice when you’re not an option to begin with.

If you can ship software here, you can ship software anywhere.

As developers write code, they can build unit testing modules directly into the code to ensure that by the time a piece of software has moved through the DevOps lifecycle, it has already been tested against most scenarios. If done correctly, this is a very efficient way to test code. Building testing modules into code requires that a fair process is in place to ensure that testing occurs throughout the entire process. Once done, this module can perform some of the duties required from a QA tester.  

Support and statements similar to ours.