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.”
Webpage designers often have aesthetic preferences and may want everyone to see their webpages in exactly the same color, size and layout. But because of their disability, many people with low vision do not see webpages the same as other people. Some see only small portions of a computer display at one time. Others cannot see text or images that are too small. Still others can only see website content if it appears in specific colors. For these reasons, many people with low vision use specific color and font settings when they access the Internet – settings that are often very different from those most people use. For example, many people with low vision need to use high contrast settings, such as bold white or yellow letters on a black background. Others need just the opposite – bold black text on a white or yellow background. And, many must use softer, more subtle color combinations.
Recent years have seen an uptick in federal lawsuits filed against businesses and governments, alleging that their website violates the ADA by being insufficiently accessible to people with disabilities. In 2017, there were at least 814 such lawsuits against organizations in a variety of industries, from banks and credit unions to restaurants and e-commerce websites. The defendants include small businesses as well as major corporations such as Nike, Burger King, and the Hershey Company.
(emphasis added). The fact that public accommodations have “flexibility” in how to comply with the ADA’s effective communication requirement has been lost in the past eight years, even though DOJ made this point in its 2010 Advanced Notice of Proposed Rulemaking (ANPRM) for websites. In that document, DOJ stated that a 24/7 staffed telephone line could provide a compliant alternative to an accessible website. The few courts to have considered this argument in the context of an early motion to dismiss have recognized its legitimacy, but have allowed cases to move forward into discovery on this and other issues. There have been no decisions on the merits addressing the viability of having a 24/7 telephone option in lieu of an accessible website.
Finally, WA11Y is another top ADA compliance plug-in to consider. A toolbox of resources to help you meet most ADA compliance needs, the plug-in packs multiple accessibility tools, each with a unique purpose. Tota11y, the first tool in the box, for instance, annotates all elements of your web pages and identifies any accessibility issues. Another tool in the box, WAVE, performs a detailed accessibility analysis of each page and provides printable reports. Then, you have FILTERS which is used to modify data within Wa11y.
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).
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.
On the legal side, ambiguity in the law and the speed at which technology and dependence on the Internet has developed created an opportunity for litigation all over our nation. As these cases have moved through our system, the courts have been nearly split -- with the 1st, 3rd and 7th Circuits ruling that the ADA does apply to websites, while the 6th, 9th and 11th Circuits have ruled that it does not. These latter rulings have all been based on the interpretation that the ADA is focused on physical location and requires a nexus test. Other circuit courts in the United States have yet to rule on the topic.
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.
Many government services and activities are also provided on websites because the public is able to participate in them at any time of day and without the assistance of government personnel. Many government websites offer a low cost, quick, and convenient way of filing tax returns, paying bills, renewing licenses, signing up for programs, applying for permits or funding, submitting job applications, and performing a wide variety of other activities.
The 2014 case involving Peapod, an online grocery retailer emphasizes that being ADA compliant goes beyond your website. The settlement required Peapod to make its mobile applications accessible by March 2015 and its website accessible by September 2015. Since mobile apps are fast becoming the preferred method of online shopping, e-commerce sites must focus on app accessibility too.
Poorly designed websites can create unnecessary barriers for people with disabilities, just as poorly designed buildings prevent some people with disabilities from entering. Access problems often occur because website designers mistakenly assume that everyone sees and accesses a webpage in the same way. This mistaken assumption can frustrate assistive technologies and their users. Accessible website design recognizes these differences and does not require people to see, hear, or use a standard mouse in order to access the information and services provided.