Internal QA can be expensive and time consuming. Here is how crowdtesting can help.
Web Accessibility was overlooked for decades. It was considered too complicated, too time-consuming, or too expensive. Luckily the world continues to progress, and governments realized that this kind of web design closed off parts of the internet to large groups of people. Now Accessibility has been written into law in many states and countries and can no longer be ignored, but all too often, the focus is simply on compliance and checking boxes on a list.
According to the World Wide Web Consortium (W3), the creators of the Web Content Accessibility Guidelines:
"Web accessibility means that websites, tools, and technologies are designed and developed so that people with disabilities can use them." Source
At first glance, this definition seems to simplify Accessibility to one thing: the ability for people with disabilities to use the Web. But let's keep reading. The page continues to say:
"More specifically, people can: (1) Perceive, understand, navigate, and interact with the Web (2) Contribute to the Web."
Many people who can't perceive, understand, navigate, interact and contribute to the Web, do not have disabilities. So, I'd like to propose an alternate definition.
Web Accessibility means that as many people as possible can perceive, understand, navigate, and interact with and contribute to the Web.
Accessibility laws make it very clear that not everyone experiences the Web the same way. In America, 20% of the population lives with at least one disability. That is 48.9 million people that may have to use tools like screen readers, ATs, or head pointers when using the Web. This number only scratches the surface of how many people are closed off from the Web. There are people with poor access to hardware, software, and Internet connectivity; people who lack computer skills; people who come from different economic situations; and these are just a few examples. All these circumstances can affect their ability to perceive, understand, navigate, and interact with the Web, and they cannot be addressed by only making sure your site is readable by a screen reader. However, they can be accounted for if you change your understanding of what Accessibility means.
Take the number of people with disabilities, 48.9 million, that we referenced above. Now add another 38.1 million people for the number of people in America living below the poverty line. Then add another 65.4 million people who speak a different language other than English at home as their first language. I could continue, but I will stop there. That is 152.4 million people out of the United States population of 328.2 million that will have problems interacting with your site if you do not make it inclusive. That is 46%! Yes, before you comment, I know that the groups I identified may have people that overlap or have people that have no problems interacting with the Web, so that number should probably be lower. However, let's not forget how few groups I mentioned in the first place. These are all people that your website could be reaching, and that won't just lead to an increase in users, it will lead to more revenue.
First, I'd like to emphasize that it is an ongoing process that starts when you first build your website and does not end after you finish it. Because no matter when it is time to publish or update, it is crucial to be considerate. Considerate of yourself and considerate of how your decisions will affect others in their various situations. Let us look at some differences between people's circumstances and how your web design can account for it.
test IO can provide you access to testers worldwide, all on real devices, in real-world conditions. So, if you want to test your site on Internet Explorer running on Windows XP, you can do it, at scale, on-demand. Or maybe you want to see how people in Ukraine, interact with your site and whether or not they can reach a specific feature. Reach out to your CSM, and we'll get you a group of people in Ukraine to test your site. Or maybe you want to know if a screen reader will work on your site regardless of the device and browser combination. Run a coverage test and have up to 50 different people on all the device and browser combinations you need let you know if various screen readers work on your site. Whatever the scenario, we'll make it happen in the real world.
Accessibility as we currently understand it is just a step in the right direction. Take it one step further by considering how inclusive it is for people who don't have disabilities, but still may struggle when interacting with your website. If the tech industry starts to do this as a whole, we can open up the Web for people of all backgrounds to create and contribute. And as a Forbes study shows, an increase in diversity helps all our bottom lines. Plus, you'll be expanding your user base and increasing your site's reach, which will help your bottom line. So why not.
If you need help making this a reality, reach out here, and we'll get you on the path to creating more inclusive software, faster.
Internal QA can be expensive and time consuming. Here is how crowdtesting can help.
I asked our CSMs what it takes to get the most from a crowdtest.
