WCAG

If you are working in the digital space, you may have heard references to a VPAT and wondered whether you need one. The answer to that question depends on what kind of digital experience you are producing as well as who your intended customers are.

Maybe. Part of the problem in answering this questions is that the Americans with Disabilities Act doesn’t mention (let alone define) web accessibility.

Of course, the easiest and most cost-effective way to have a WCAG compliant website is to build it that way in the first place. And while it’s never too late, the absolute best time to start thinking about accessibility is when you are planning your site’s user experience (UX) and designs.

Websites that are inaccessible make it harder for customers with disabilities to use their sites. At any given moment, roughly 20% of the US population has a disability. It follows that improving web accessibility results in higher engagement and conversion rates. Which ultimately means more revenue for your business.

If you are new to the topic of web accessibility, there is a lot to absorb about what it means to make your website accessible. Some common accessibility issues are inherent to the way your site was coded while others have more to do with the content that you populate into your site.