In short, the ADA is meant to protect disabled individuals as they go about their daily lives. These regulations ensure that people with disabilities are not denied entry into the above places or denied services by a company due to their disability. It is important to note that these regulations are now applicable to services that are provided online or through other digital formats. For example, if a company accepts job applications online, then it must ensure that a person with a disability can also apply for the job online. In other words, it is illegal to have barriers on the website that would keep the disabled individual from successfully completing their application. Fortunately, the ADA guidelines help to remove barriers and ensure that the Internet remains a space that people of all backgrounds and disabilities can use.
Leading web developers have been pioneering accessibility and publishing standards since 1994. In 1999, the Web Accessibility Initiative (WAI) and the World Wide Web Consortium (W3C) created the Web Content Accessibility Guidelines (WCAG). In essence, the people who determine how the internet is written came together to advise web developers on how to make websites accessible not only to people with disabilities, but to all web users, including those with highly limited devices.
In recent cases, the U.S. Department of Justice has repeatedly sided with plaintiffs arguing that a private company’s website needs to be accessible, despite any other mitigating factors. One thing is for certain, however: The number of federal lawsuits alleging violations of the ADA is currently accelerating at a rapid pace. Between January and August 2017, there were 432 ADA lawsuits filed in federal court—more than the total number of ADA lawsuits in 2015 and 2016 combined.
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 WP.org 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 WP.org 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!
The landscape of disabled access litigation related to online services has significantly changed and expanded over the past decade. Initially, the internet was an area of little concern as courts uniformly held that the ADA applied to "brick and mortar" facilities, not to cyberspace. This has changed and online accessibility is presently, and will continue to be, an area of significant investigation and litigation.
WordPress themes designed with accessibility in mind tend to be easier to use and clearer to navigate than their contemporaries. While you may have specific goals in mind like ADA compliance or WCAG 2.0 standards to pass, rest assured that you won’t have to sacrifice on design quality. You’ll likely find a theme with a higher standard of design by searching for templates with these requirements.
The Federal Communications Commission (FCC) enforces regulations covering telecommunication services. Title IV of the ADA covers telephone and television access for people with hearing and speech disabilities. It requires telephone and Internet companies to provide a nationwide system of telecommunications relay services that allow people with hearing and speech disabilities to communicate over the telephone.
@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.
Until the ADA is updated to address the special case of website accessibility, or the Department of Justice releases its website accessibility regulations, complying with WCAG 2.0 Level AA is the best way to ensure that people with disabilities have equal access to your website. The overview below is a great starting point about meeting the WCAG 2.0 Level AA recommendations.
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.