This is particularly important when working for a government agency or government contractor, as these organizations must follow web accessibility guidelines under Section 508 of the Workforce Rehabilitation Act of 1973. Although ADA and Section 508 compliance are different, the published checklist for Section 508 compliance offers insight into ways to make websites accessible for people with disabilities, and thereby work toward ADA compliance.
Imagine struggling to do something as simple as navigating and reading a website, when you’re suffering from Glaucoma, Cataracts, Macular degeneration, Retinal disorders, Refractive errors, Optic nerve disorders, and other eye issues. Reading the text in order to gain knowledge and information, would be tiring at the least. Your website doesn’t need to be like that, in fact, your website can be a pleasant experience where the visually impaired can easily zoom in and out on every page or, the text to speech feature will convert to the audible voice that you are listening to right now.

Up-to-date standards are offered for checking compliance, and it provides a cost-effective way to scan a site for compliance. There's services out there where it'd cost more than $150 (the current cost of a 1 site 1 year license) for the size of the sites I'm working with. I'm very happy to see this offering in the first place, and it's even nicer to see how thorough it looks to be. Of course, it's not perfect so I'd love to see more of the listing fleshed out (the developer author/contributor mention is missing, etc.), I'd love to see the free version on GitHub (or similar for community development assistance [I have a few things I'd help with] which is very nice to see in a listing to show there's support / ongoing development for the plugin), and of course I'd love to see the server-side checker come to feature-parity with WAVE (currently WAVE is showing a few things the server-side checker doesn't have [color contrast, etc.]) Keep up the great work!
Hi Ashley, Thanks for the feedback. However, I respectfully disagree about JAWS. There was a time many years and versions ago when screen readers didn't support id attributes as targets, but that's no longer true. I just tested my site with JAWS 14 in both IE9 and Firefox 17. In both browsers JAWS identifies the link as "Same page link Skip to main content", then if I click on that link using the left mouse button I jump directly to the "main region", and a couple of down arrows later I'm on the main heading. I actually wrote an earlier blog post about this very topic.
Vu said that she gets one question all the time: What are the legal standards? There is no legal standard, but there are guidelines out there: The Web Content Accessibility Guidelines (WCAG), version 2.0, with 3 levels of conformity: A, AA, AAA. They were put out by W3C. Companies can use those guidelines. The Justice Dept. uses the A and AA levels.
The Americans with Disabilities Act (ADA) was first passed in 1990. Twenty years later, the US Department of Justice released an update called the 2010 ADA Standards for Accessible Design. These standards cover the design of physical spaces and have been interpreted to include web locations as well, so it can be difficult for the would-be accessible website designer to use them.