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.”
You may have installed a ramp, increased the width of your door frames, or made other accommodations to ensure that your physical premises are accessible to all. The requirement for equal access used to only apply to physical locations and storefronts, but now the government is actively ensuring that the requirements for ADA accessibility include online properties such as websites and mobile apps.
If you do get sued, if you immediately remediate your website, you may be able to get the lawsuit dismissed on mootness (there’s no longer anything in dispute, i.e. plaintiffs are arguing your website is inaccessible but you’ve already made it accessible). This definitely does not mean you should wait to fix your website but it does mean you may have an out.
This plug-in has been around for some time. Recently they were even advising users to uninstall the old version and install a new one. The new version comes with Skip menus, a button to reset font size, a Skip link inside the accessibility sidebar, and a DOM scanner that automatically checks pages and published posts for accessibility errors such as issues in image ALT, titles, and links. Contrast adjustment, color filters, lights off mode, and link highlighting are the other standout features.
The Americans with Disabilities Act (ADA) and, if the government entities receive federal funding, the Rehabilitation Act of 1973 generally require that state and local governments provide qualified individuals with disabilities equal access to their programs, services, or activities unless doing so would fundamentally alter the nature of their programs, services, or activities or would impose an undue burden.2 One way to help meet these requirements is to ensure that government websites have accessible features for people with disabilities, using the simple steps described in this document. An agency with an inaccessible website may also meet its legal obligations by providing an alternative accessible way for citizens to use the programs or services, such as a staffed telephone information line. These alternatives, however, are unlikely to provide an equal degree of access in terms of hours of operation and the range of options and programs available.
In January of 2017 the federal government moved forward with the adoption of WCAG 2.0 AA as the standard for federal agency sites, leading many in the accessibility community to believe that a full adoption of the WCAG 2.0 Level AA standards by the DOJ for websites both public and private would be forthcoming. As of the writing of this post, that has neither occurred nor been added to the DOJ’s agenda, likely due to the installation of a new administration and other legislative priorities.
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.
Enacted in 1990, this civil rights statute was created for the purpose of limiting discriminatory practices towards individuals with disabilities. This act and its amendments guarantee equal opportunity for persons with disabilities in employment, state and local government services, public accommodations, commercial facilities, and transportation. Both public and private entities are affected by the ADA.
When the Americans with Disabilities Act became law in 1990, modern communications technologies such as the Internet were still in their infancy. The past few decades, however, have seen the rise of new channels such as websites and mobile applications, raising questions about the ADA’s original mission to make U.S. society more accessible to people with disabilities.
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.
If your hotel used responsive web design when creating your online marketing strategies, you’re already meeting many of the ADA compliant regulations for hotel websites. You will still need to make some changes, but you definitely have a head start. Making the changes now, before your business is the target of a lawsuit or government action, makes good business sense.
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.
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.
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!
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.
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.