The ADA requires that title II entities (State and local governments) and title III entities (businesses and nonprofit organizations that serve the public) communicate effectively with people who have communication disabilities. The goal is to ensure that communication with people with these disabilities is equally effective as communication with people without disabilities.
Businesses and nonprofits: in determining whether a particular aid or service would result in an undue burden, a title III entity should take into consideration the nature and cost of the aid or service relative to their size, overall financial resources, and overall expenses. In general, a business or nonprofit with greater resources is expected to do more to ensure effective communication than one with fewer resources. If the entity has a parent company, the administrative and financial relationship, as well as the size, resources, and expenses of the parent company, would also be considered.
The Department of Justice published revised final regulations implementing the Americans with Disabilities Act (ADA) for title II (State and local government services) and title III (public accommodations and commercial facilities) on September 15, 2010, in the Federal Register. These requirements, or rules, clarify and refine issues that have arisen over the past 20 years and contain new, and updated, requirements, including the 2010 Standards for Accessible Design (2010 Standards).
While legal considerations might be your biggest worry, making your site more accessible is simply good customer service. More than 39 million Americans are blind and another 246 million have "low vision," Another one million are deaf in the U.S. Add to that people with mobility issues that prevent them from using their hands and that's a huge portion of the country's buying power.
I should mention one caveat to all of this. Businesses that are required to comply but don't have the ability to bring their websites into compliance can provide an accessible alternative to provide the same information, goods, and services that they provide online, like a staffed phone line. The trick, however, is that this option has to provide at least equal access, including in terms of hours of operation. And, as we know, the internet is around 24/7, so good luck with that.
When the Americans with Disabilities Act (ADA) was first passed in 1990, the internet had yet to take off. However, the ADA has realized the importance of including online spaces within its parameters. If your business is considered a ‘place of public accommodation,’ then your website must be ADA compliant. Multiple rulings from judges have set legal precedent that websites must be accessible and are at risk of heavy fines and penalties when they are found not compliant. Winn-Dixie is the latest business to learn this the hard way.
Craig facilitates the execution of each project from start to finish, helping you convey your vision and bring it to life. Craig’s primary objective is to make certain that all of your needs are addressed throughout the project, from detailed technical specifications to assisting with collecting assets. This allows the staff of Quantum Dynamix to focus on what they do best; creating innovative work that meets your objectives.
Until the ADA is updated to address the special case of website accessibility, or the Department of Justice releases its website accessibility regulations, complying with WCAG 2.0 Level AA is the best way to ensure that people with disabilities have equal access to your website. The overview below is a great starting point about meeting the WCAG 2.0 Level AA recommendations.
An example is Patagonia Works, Inc. which had a complaint for a permanent injunction filed against it in the United States District Court stating, Under Section 302(b)(1) of Title III of the ADA, it is unlawful discrimination to deny individuals with disabilities an opportunity to participate in or benefit from the goods, services, facilities, privileges, advantages or accommodations, which is equal to the opportunities afforded to other individuals. 42 U.S.C. 12182 (b)(1)(A)(ii). Below is a summary of what the lawyers asked the court for.
Hi Ashley, Thanks for the feedback. However, I respectfully disagree about JAWS. There was a time many years and versions ago when screen readers didn't support id attributes as targets, but that's no longer true. I just tested my site with JAWS 14 in both IE9 and Firefox 17. In both browsers JAWS identifies the link as "Same page link Skip to main content", then if I click on that link using the left mouse button I jump directly to the "main region", and a couple of down arrows later I'm on the main heading. I actually wrote an earlier blog post about this very topic.
You probably won't have to check your site with all of the available evaluation tools out there, but it is a good idea to do so for the most common web browsers. Just as accessibility software makes it easier for people with disabilities to navigate the Internet, these tools make it easier for developers to ensure accessibility from the start. When you think you've mastered it, go back through the Section 508 compliance checklist to ensure you've met every goal.