Maybe you’ve heard about web accessibility on a podcast or heard a developer friend talking about it. Maybe you’ve thought to yourself you should learn more and start implementing web accessibility standards on your site. Maybe you were gung-ho to get started, but were stopped dead in your tracks when you hit the mass volume of difficult-to-read guidelines. Let’s be honest, web standards for accessibility are overwhelming. The WCAG 2.0 guidelines are lengthy and legal sounding. Add to that the varying levels of accessibility (A, AA, AAA), along with some gray areas in-between. Finally, the site design looks like a throw back to early web: an intimidating wall of text that goes on and on (which is technically accessible, but not a great user experience). What’s a web developer to do? You want to help make the web more accessible, but you don’t know how to actually do it. Web Accessibility Defined Let’s start by getting on the same page about what web accessibility is. It’s more than just making your website look good on mobile or being screen-reader friendly. It’s about creating a website in such a way that anyone can access that content regardless of the device used to consume the content.
Share This

We are using cookies on our website

Please confirm, if you accept our tracking cookies. You can also decline the tracking, so you can continue to visit our website without any data sent to third party services.