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.
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).
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.
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.
It makes sense that everyone should have equal access to websites and online properties. The Internet has become an integral part of our lives, where we go to shop, learn, do our banking, and socialize. The DOJ hasn’t determined what the final set of regulations for ADA compliant websites will be yet, but there are established guidelines and standards of accessibility that can be viewed on the ADA website. Once a website meets these accessibility standards it qualifies as ADA compliant.
(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.
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.
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.
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.