alternative text

Take a look at your town’s website. I was checking out my local township website to get some election related information last week. And it’s kind of awful. For everyone. But especially for users with disabilities.

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.

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.

Everyone has to start somewhere. We are often asked where organizations should focus their initial efforts. This post is our attempt to sketch out a bare minimum; this isn’t enough but it should go a long way in improving your site’s user experience for all users while also reducing your risks of being sued under the ADA.