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.”
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.
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.
About the Speaker: Bill Mitchell is the co-founder and Chief Operating Officer of RezStream, a company dedicated to hospitality solutions, located in Denver, Colorado. Bill has over 30 years experience in the hospitality industry with extensive knowledge in consulting, sales, support, website design and Internet marketing.RezStream sells reservation software (RezStream Professional PMS), online reservation booking engine services (RezStream Rez2u Booking Engine), Global Distribution System services, custom website designs, and Internet marketing services.
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.
Many people with disabilities use assistive technology that enables them to use computers. Some assistive technology involves separate computer programs or devices, such as screen readers, text enlargement software, and computer programs that enable people to control the computer with their voice. Other assistive technology is built into computer operating systems. For example, basic accessibility features in computer operating systems enable some people with low vision to see computer displays by simply adjusting color schemes, contrast settings, and font sizes. Operating systems enable people with limited manual dexterity to move the mouse pointer using key strokes instead of a standard mouse. Many other types of assistive technology are available, and more are still being developed.
The ADA itself holds different organizations to more/less stringent standards based on a host of factors, government funding being a major one. Government agencies themselves are usually held to the most severe standards. That said, while ADA has adopted WCAG as the defacto standard, from what I’ve seen it appears they’re going with AA compliance as the most reliable one. That said, we’ve done work with some organizations who’ve chosen to comply with AAA in an effort to be as buttoned up as possible from an accessibility and experiential perspective. We’ve also worked with some who have tighter budgers and aim for level A compliance and have a more “react and repair” mindset when they discover anything in their site that is giving someone hardship from an accessibilirt standpoint.
Olmstead v. L.C. was a case before the United States Supreme Court in 1999. The two plaintiffs L.C. and E.W. were institutionalized in Georgia for diagnosed mental retardation and schizophrenia. Clinical assessments by the state determined that the plaintiffs could be appropriately treated in a community setting rather than the state institution. The plaintiffs sued the state of Georgia and the institution for being inappropriately treated and housed in the institutional setting rather than being treated in one of the state's community based treatment facilities.
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!
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.
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.
This past September marked the first time a judge ruled that the ADA applies even to businesses without a physical location. Scribd, an e-book subscription service is considered to provide "a place of public accommodation." Their services are not accessible to blind persons because they cannot be read with a screen reader. The judge reasoned, "Now that the Internet plays such a critical role in the personal and professional lives of Americans, excluding disabled persons from access to covered entities that use it as their principal means of reaching the public would defeat the purpose of this important civil rights legislation."
This guidance document is not intended to be a final agency action, has no legally binding effect, and may be rescinded or modified in the Department's complete discretion, in accordance with applicable laws. The Department's guidance documents, including this guidance, do not establish legally enforceable responsibilities beyond what is required by the terms of the applicable statutes, regulations, or binding judicial precedent.
What’s in store for 2018? If the Ninth Circuit upholds the Domino’s district court’s dismissal on due process grounds, the number of California website accessibility lawsuits in federal court may go down dramatically. Even if that occurs, we see no end to the website accessibility lawsuit surge elsewhere and expect that new plaintiffs’ firms will continue to enter the scene. While the current administration’s DOJ is not likely to push the website accessibility agenda, its inaction will not stop the lawsuits. Only an amendment to the ADA can do that, which we believe is highly unlikely. Thus, the best risk mitigation effort for covered entities is still to make their websites accessible as soon as possible, with the assistance of ADA Title III legal counsel experienced in website accessibility issues and reputable digital accessibility consultants.
Jeremy I am an artist and designer. The business I would like to have a website for is painting pet portraits. I also paint them with their owners, kids, etc. The reservations I have about the (template choice) website plans is that none of the templates I have seen show what I do well enough. Is there a site where I can setup or design my own homepage image without using a prescribed template?
Conclusion: This article covers only the basics behind ADA accessible websites. You can find further detailed information at www.ada.gov. Since most current websites are not yet fully ADA accessible, it is important for you to begin the process now. But be forewarned. The consequences of not becoming ADA accessible can be expensive. The potential of penalty fees, lawsuits, and lost business are all powerful reasons to be ahead of the curve when it comes to ADA accessibility for your website. To make sure your website meets the necessary ADA guidelines, select a website design and consulting firm that specializes in ADA accessible websites and online reservation systems. As always, RezStream is happy to assist lodging properties of all sizes in ADA consulting and website design services. Please call RezStream toll-free at 866-360-8210 for more information on this timely topic.
The Department of Justice (DOJ) has specifically stated in rulings that websites should be designed so they are accessible to individuals who have vision, hearing, and physical disabilities. There’s a growing body of case law where the DOJ required companies to provide an ADA compliant website and levied hefty penalties when sites failed to measure up.
In court, Netflix tried to argue that websites should not be part of ADA compliance regulations, as there is no physical structure / location. They also argued that websites should not be in scope of ADA as there is no public component (the original ADA compliance law specifically called out that ADA rules apply primarily to services, locations, and products that are supposed to be open to the public).
Now you know that some types of content and format on webpages can pose barriers for people with disabilities. The next steps are to develop an action plan to fix web content that is currently inaccessible and implement procedures to ensure that all new and modified web content is accessible. The website accessibility checklist included in this section helps you assess what needs to be done.
Government Code §11546.7 – The requirement that state agency heads certify, every two years, that their agency’s website meets the Web Content Accessibility Guidelines, Version 2.0 or a subsequent version, at Level AA or higher, and the requirements of Sections 11135 and 7405 of the Government Code. Created by AB 434 (Baker, Chapter 780, Statutes of 2017), and sometimes referred to as AB 434.
Spector v. Norwegian Cruise Line Ltd. was a case that was decided by the United States Supreme Court in 2005. The defendant argued that as a vessel flying the flag of a foreign nation it was exempt from the requirements of the ADA. This argument was accepted by a federal court in Florida and, subsequently, the Fifth Circuit Court of Appeals. However, the U.S. Supreme Court reversed the ruling of the lower courts on the basis that Norwegian Cruise Lines was a business headquartered in the United States whose clients were predominantly Americans and, more importantly, operated out of port facilities throughout the United States.