Tags: 2.0, 2.1, 2010, accessibility, ADA, Advanced Notice of Proposed Rulemaking, ANPRM, attorney general, Congress, Department of Justice, Due Process, effective communication, House of Representatives, Interpretation, Jeff Sessions, June, Legal Action, litigation, motion to dismiss, public accommodations, September 25, Staffed Telephone, Standards, Statutory Authority, Title III, WCAG, Web Content Accessibility Guidelines, website
UPDATE: Since writing this post in August 2017, several important changes have taken place in the laws regarding ADA compliance for websites. On December 26, 2017, the Department of Justice announced that they have withdrawn the Obama-era Advance Notice of Proposed Rulemaking mentioned in this article which intended to require ADA website compliance. The DOJ’s withdrawal announcement stated, “The Department will continue to assess whether specific technical standards are necessary and appropriate to assist covered entities with complying with the ADA.”
The Department is evaluating whether promulgating regulations about the accessibility of Web information and services are necessary and appropriate. Such an evaluation will be informed by an additional review of data and further analysis. The Department will continue to assess whether specific technical standards are necessary and appropriate to assist covered entities with complying with the ADA.
The words in the tag should be more than a description. They should provide a text equivalent of the image. In other words, the tag should include the same meaningful information that other users obtain by looking at the image. In the example of the mayor’s picture, adding an “alt” tag with the words “Photograph of Mayor Jane Smith” provides a meaningful description.
VERY useful. I searched for a plugin that had WAVE scanning integrated and this plugin came up. I was a bit hesitant because there were only a few reviews and the price was higher than most plugins. However, if the plugin worked, it would save me $1,000 from requesting a WAVE scan of my entire site. In short, this plugin is amazing. It is super-detailed. That makes it a bit longer to learn and master. However it makes it amazingly useful. If you take compliance seriously, this is the plugin for you. I am not a developer, but understand more about coding than the average content creator. I was able to understand this plugin, though it took several hours. Don't take that as a bad thing. It was necessary, and I learned a TON about ADA compliance in the meantime. When I had a question, the author was super-fast and helpful. I highly recommend this plugin.
Another important consideration is that the ADA does not allow businesses to simply provide an alternative such as a phone number. Lastly, include accessibility issues as part of your website and mobile strategy. When new technologies are implemented or pages added, part of the process should include the implications for persons with disabilities.
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!
Your site would need to have a text only option, with all functionality accessible through a keyboard for visitors with mobility issues. Once you make these and other changes to meet ADA guidelines, your site would need to be tested by a website development company familiar with ADA compliance issues to be sure that visitors who use assistive technology such as screen readers are able to access your web content fully.
Because the ADA does not specifically mention websites, it also does not outline standards for how organizations can make their websites accessible. However, the DOJ has frequently cited recommendations such as the Web Content Accessibility Guidelines (WCAG) 2.0 as acceptable metrics for accessibility. WCAG 2.0 includes many different criteria at three different “success levels” of accessibility, ranging from high-contrast color schemes to closed captions for video content.
In response to the members’ concern about the proliferation of website litigation lawsuits, DOJ said: “Given Congress’ ability to provide greater clarity through the legislative process, we look forward to working with you to continue these efforts.” DOJ is essentially putting the ball back in the Congressional court, where little is likely to happen.
On Dec. 26, 2017, the DOJ withdrew the proposed rulemaking for Title II and Title III, effectively killing any forward progress on adoption (more on that here: https://www.law.com/dailybusinessreview/2018/03/01/website-operators-are-on-notice-recent-events-may-force-change/). While disappointing, this is not surprising, given the current administration's commitment to deregulation. That said, I fully expect the courts to continue to fill the gap and hold businesses accountable, so I would encourage you to take accessibility standards into account as you work up the governance for your enterprise intranet services. If it would be helpful for me to put you in touch with an attorney with experience in these matters, I'd be more than happy to do so. Feel free to shoot me an email anytime at [email protected] Best of luck!
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 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.”
Accessibility is important and should be a part of your company or organization’s long-term digital presence strategy. As the web grows ever more refined and personalized, it will no longer be just other entities like the government, Google and the DOJ that expect your site to function with all possible populations in mind. Individual users of all backgrounds, abilities and experience will expect and demand that your site be clear, easy to use and accessible to all.