Absent the adoption of specific technical requirements for websites through rulemaking, public accommodations have flexibility in how to comply with the ADA’s general requirements of nondiscrimination and effective communication. Accordingly, noncompliance with a voluntary technical standard for website accessibility does not necessarily indicate noncompliance with the ADA.
In January of 2017 the federal government moved forward with the adoption of WCAG 2.0 AA as the standard for federal agency sites, leading many in the accessibility community to believe that a full adoption of the WCAG 2.0 Level AA standards by the DOJ for websites both public and private would be forthcoming. As of the writing of this post, that has neither occurred nor been added to the DOJ’s agenda, likely due to the installation of a new administration and other legislative priorities.

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 ADA guidelines provide the foundation that organizations need to achieve digital accessibility best approaches, however they are not exhaustive. They do not provide direction for all of the accessibility challenges that people with disabilities face. They also fail to provide detailed technical instructions. With these limitations in mind, there is a ray of hope.
Federal law isn't the only consideration for businesses. Additionally, each state interprets the law differently. Consider the case against Netflix in 2012. Lawsuits were brought in federal court in Massachusetts and California. Netflix was accused of violating the ADA by not offering "closed captioning" options for its Internet streamed movies. Illustrating the complexity of this issue, the courts reached completely opposite decisions. Massachusetts held that Netflix must comply with the ADA, while the California court found that Netflix did not fall under the ADA's definition of "public accommodation."

You may have installed a ramp, increased the width of your door frames, or made other accommodations to ensure that your physical premises are accessible to all. The requirement for equal access used to only apply to physical locations and storefronts, but now the government is actively ensuring that the requirements for ADA accessibility include online properties such as websites and mobile apps.
Under Title II, publicly available videos, whether for entertainment or informational use, must be made accessible to individuals with disabilities. That means including captions on videos both in person and online so that deaf and hard-of-hearing people can access public services. Websites for public entities should also be fully accessible to users who are deaf, blind or have limited dexterity.

Without a definitive ruling, there is room for a difference of opinion. That’s exactly what happened in 2015 in the 9th Circuit Court of Appeals, which ruled that Netflix is not subject to Title III of the ADA because it has no physical place of business. This opinion was unpublished, meaning it is not intended to be considered legal precedent, but it certainly makes it confusing for businesses that are not sure where they stand under the ADA.

Basically, there are standards which apply to US federal agencies, and State or Local Government websites (not business/personal websites). While some disability discrimination laws do mention websites, they don’t specify the technical standards required to comply with the law. Regardless of ADA’s lack of stating websites must be fully accessible, the Department of Justice seems to rule on the side of “they should be”.
Use the plugin, follow its instruction, and resolve the compliance issues identified. You’ll find that using the plugin will save you an incredible amount of time as you maintain your site’s compliance on a month-to-month basis. The best part, it identifies the compliance issues and tells you exactly which code elements are out of compliance and why! Our average customer is reporting a 10x-20x time savings over manually identifying and fixing these problems. In extreme cases more than 30x time savings has been reported! Using the plugin alone does not guarantee compliance. Some parts of accessibility can’t be automatically scanned and must be manually audited but we also provide independent 3rd-party audits and certifications of compliance. The Accessibility Suite Pro Plugin for WordPress makes this process profoundly easier.
Use the plugin, follow its instruction, and resolve the compliance issues identified. You’ll find that using the plugin will save you an incredible amount of time as you maintain your site’s compliance on a month-to-month basis. The best part, it identifies the compliance issues and tells you exactly which code elements are out of compliance and why! Our average customer is reporting a 10x-20x time savings over manually identifying and fixing these problems. In extreme cases more than 30x time savings has been reported! Using the plugin alone does not guarantee compliance. Some parts of accessibility can’t be automatically scanned and must be manually audited but we also provide independent 3rd-party audits and certifications of compliance. The Accessibility Suite Pro Plugin for WordPress makes this process profoundly easier.
“Streaming of video programming over the Internet—by defendant Netflix and other similar providers—has revolutionized the entertainment industry; it is fast becoming the dominant means of delivering movies, television shows, and other entertainment offerings to the American public. Persons who are deaf or hard of hearing should not be prevented from fully participating in this aspect of American life. Netflix’s denial of equal access to, and full enjoyment of, its “Watch Instantly” service violates the ADA.”-Assistant Attorney General, Thomas E. Perez.
In an August 2016 case involving the University of California Berkeley, the DOJ ruled that the public university was in violation of ADA Title II (similar to Title III but it instead applies to government organizations) because their YouTube channel’s videos didn’t include captions for hearing impaired visitors. The DOJ found this to violate the ADA as deaf users did not have equal access to the online content.
Legal precedent is changing, and ADA compliance related lawsuits are becoming more successful, and the courts are seeing more of them as a result. Title III of the Americans with Disabilities Act pertains to private sector businesses. Lately, those protections are more frequently expanding into digital territory as web and mobile applications become more necessary in our day-to-day lives.
For example, you may have thousands of images on your website that need to be checked for the presence of “alt text,” which is a requirement under WCAG 2.0. This is a task for automated testing software, which can perform the job much faster than any human. While automated tools can detect if the images on your website have alt text, however, they aren’t able to determine whether the text is correct and meaningful—which is a job for human testers.

Talk to your web designer about other techniques that will make your site more user-friendly for people with disabilities. Worried that’s not in your budget? Consider the fact that DOJ fines start at $75,000. And it's still yet to be determined if a non-compliant website is liable for one fine or will be charge per page for each violation. As the recent lawsuits illustrate, though, settlements quickly add up into the millions.
The Department has assembled an official online version of the 2010 Standards to bring together the information in one easy-to-access location.  It provides the scoping and technical requirements for new construction and alterations resulting from the adoption of revised 2010 Standards in the final rules for Title II (28 CFR part 35) and Title III (28 CFR part 36).
×