The statement that “noncompliance with a voluntary technical standard for website accessibility does not necessarily indicate noncompliance with the ADA” is new and significant. It is a recognition that a website may be accessible and usable by the blind without being fully compliant with the privately developed Web Content Accessibility Guidelines (WCAG) 2.0 or 2.1. The statement confirms what some courts have said so far: That the operative legal question in a website accessibility lawsuit is not whether the website conforms with WCAG, but whether persons with disabilities are able to access to a public accommodation’s goods, services, and benefits through the website, or some alternative fashion.
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.
Peter is Founder and CEO of Blue Interactive Agency, a full service digital marketing agency. With a passion for online marketing, Peter enjoys analyzing digital strategies and offering his unique view on how effective they are. Having a track record of successfully commercializing digital properties, Peter is always looking for the next challenge to help a company succeed online. In his spare time, Peter maintains a personal blog which focuses on his gastronome adventures.
In some circumstances, longer and more detailed text will be necessary to convey the same meaningful information that other visitors to the website can see. For example, a map showing the locations of neighborhood branches of a city library needs a tag with much more information in text format. In that instance, where the map conveys the locations of several facilities, add a “longdesc” tag that includes a text equivalent description of each location shown on the map – e.g., “City Center Library, 433 N. Main Street, located on North Main Street between 4th Avenue and 5th Avenue.”
It is worth noting that before the settlement, Netflix attempted to argue that, due to its role as a streaming video distributor, any legal action should pertain to the 21st Century Communications and Video Accessibility Act (CVAA), which, at the time, did not call for closed captions on content that had not previously aired on US television. However, the court ruled that these two laws are not mutually exclusive and that Netflix was not protected from ADA prosecution because of compliance with the CVAA.
As a web developer, Ryan's work is what makes the magic happen. He spends most of his time creating custom websites, which involves turning the designers' visual mockups into code. It's lucky that he's such a good problem solver, because many of Ryan's projects involve working with clients to create complex custom functions. He's also one of the few developers in the country with extensive experience developing for the HubSpot CMS.
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.
Meanwhile, the tech community and our courts system were forced to deal with the issue on their own. First, the tech community coalesced around a set of standards via the World Wide Web Consortium, establishing the Web Content Accessibility Guidelines in 2008 and later updating them in 2012 (WCAG 2.0), when they were also adopted as an ISO standard. Today, web designers and developers across the world use WCAG 2.0 to guide their design and development, typically aiming to meet all of the standards under Level AA.
DOJ’s September 25 response did not do what the members asked, but it did provide some helpful guidance and invited Congress to take legislative action to address the exploding website accessibility litigation landscape. DOJ first said it was “evaluating whether promulgating specific web accessibility standards through regulations is necessary and appropriate to ensure compliance with the ADA.” (This is helpful – to at least know this issue has not fallen totally off DOJ’s radar.) It continued:
Develop a plan for making your existing web content accessible. Describe your plan on an accessible webpage, and encourage input on how accessibility can be improved. Let visitors to your website know about the standards or guidelines that you are using to make your website accessible. When setting timeframes for accessibility modifications to your website, make more popular webpages a priority.