Web Accessibility and Reduced Resource Utilization
This blog post is part of a series of posts discussing the Business Case for Accessibility. In order to get a full view of the Business Case for Accessibility, I encourage you to read all posts in this series, links to which can be found at the bottom of this post.
Some argue that relying on more standards-based production techniques will save money by reducing resource utilization – particularly bandwidth. They state that doing things like using CSS instead of tables and spacer images, and eliminating “tag soup”-riddled markup will cause a decrease in hardware-related resources needed for a website due to reduced document weight.
- Does it increase income? No. Reduced resource utilization is about saving money
- Does save money? Probably not significantly, as I’ll discuss below
- Does it mitigate risk? No.
- How strong is the evidence? Weak. I have seen no recent evidence to suggest that document size has a significant impact on a company’s bandwidth or hosting bill.
It seems to make sense: Use less of something and that thing will cost less money. The thing is that these days bandwidth and server space is pretty cheap. When it comes to very large companies, their bandwidth and data storage needs are impacted by a lot more things than just a website.
Overall, I’d say I’m skeptical of this purported benefit. If anyone out there has any first-hand data to share on this topic, please get in touch. If you wish to be anonymous, I will honor your request.