This site should be available to anyone on any device from anywhere they’re able to access the internet—regardless of the speed of their connection.11Ethan Marcotte also has an accessibility page that’s worth looking at. It would be great to see more of these around the web. I’ve taken steps to ensure this site is accessibile as it can be both from a visual design and a technology and performance standpoint and aim for AA WCAG 2.1.
If there’s anywhere I’ve made a mistake or can otherwise improve the accessibility of the site, you can send an email to firstname.lastname@example.org, and I’ll make it a priority to research and understand how to improve and then implement the improvements. I’ll usually even write an article here about what I learned and what I changed to improve the accessibility. And I’ll always give you credit for bringing it to my attention.
If you’re not already familiar with accessibility, the WAI’s Accessibility Fundamentals site is a good place to start. They also offer a handy WCAG quick reference that provides a good overview of how to ensure a site is accessible.
They also provide a good video overview of web accessibility that helps explain the breadth of accessibility options and the ways in which accessibility benefits everyone that uses your site.
A Word on Accessibiilty Overlays
While accessibility overlays may be attractive as a way to throw money at a “problem”, they’ve generally been found to hinder accessibility more than they help, and you should likely avoid using them. If you’d like more specific information, Adrian Roselli has extensively documented the problematic nature of accessibility overlays, law suits related to them, and the bad behavior of the companies selling them.