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.
The Department of Justice’s revised regulations for Titles II and III of the Americans with Disabilities Act of 1990 (ADA) were published in the Federal Register on September 15, 2010. These regulations adopted revised, enforceable accessibility standards called the 2010 ADA Standards for Accessible Design, "2010 Standards." On March 15, 2012, compliance with the 2010 Standards was required for new construction and alterations under Titles II and III. March 15, 2012, is also the compliance date for using the 2010 Standards for program accessibility and barrier removal.
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.
Hey Casey, this is one of the areas where things get a little weird because the W3 doesn’t actually have any say over the ADA guidelines, it is more than the ADA guidelines adopted the WCAG 2.0 guidelines as just that, a guideline to help. As far as I know, the tool you’ve linked to hasn’t been used in any judgements I’m aware of. Usually when it comes down to making a decision on if something is/isn’t compliant they have people use the actual PAWS tools and show what elements do/don’t work as intended or are otherwise inaccessible. Hope this helps!
Courts have taken essentially the following position on the issue of whether websites are places of public accommodation: Website accessibility fulfills the spirit of the ADA by lowering the barriers for people with disabilities to participate in business and commerce. As such, commercial websites need to comply with ADA regulations. Judges have reached this conclusion in several high-profile cases, such as the National Federation of the Blind’s lawsuit against the Scribd digital library. As a result of this case, Scribd agreed to redesign its website to work with screen reader software by the end of 2017.
If the user selects this button, the page is read aloud while text is highlighted. This is powered by ReadSpeaker, which I think is a really cool product. It provides improved accessibility to a vast audience of people who might not otherwise have their own assistive technology, such as people who are not native to the language of the page, or people with dyslexia or other reading challenges.
Another federal agency, the Architectural and Transportation Barriers Compliance Board (ATBCB), also known as the Access Board, issues guidelines to ensure that buildings, facilities and transit vehicles are accessible to people with disabilities. The Guidelines & Standards issued under the ADA and other laws establish design requirements for the construction and alteration of facilities. These standards apply to places of public accommodation, commercial facilities, and state and local government facilities.
@Rick, I didn't specifically look at doctype, but Steve Faulkner did in his original article (see the link at the top of this post). He found that 101 of the 130 pages containing role="main" (78%) used the HTML5 doctype, which of course leaves 22% that didn't. I do recommend using ARIA even if using an earlier doctype. Validation is important, but if validation and accessibility conflict, I think most would agree accessibility should trump validation. Assistive technologies that support ARIA landmarks do so regardless of doctype, and otherwise the presence of these role attributes has no ill effects in any user agent.
The ADA requires that title II entities (State and local governments) and title III entities (businesses and nonprofit organizations that serve the public) communicate effectively with people who have communication disabilities. The goal is to ensure that communication with people with these disabilities is equally effective as communication with people without disabilities.