A. No. The ADA does not require that an employer hire an applicant with a disability over other applicants because the person has a disability. The ADA only prohibits discrimination on the basis of disability. It makes it unlawful to refuse to hire a qualified applicant with a disability because he is disabled or because a reasonable accommodation is required to make it possible for this person to perform essential job functions.
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.
Because of this, among the greatest drivers of website accessibility are usability improvements and the reputation boost that it brings—or, alternatively, the lost business that organizations want to avoid as a result of inaccessible websites. According to a survey by the National Business Disability Council at the Viscardi Center, 91 percent of customers say that they’d prefer to shop at a website that prioritizes accessibility.
"III-3.6000 Retaliation or coercion. Individuals who exercise their rights under the ADA, or assist others in exercising their rights, are protected from retaliation. The prohibition against retaliation or coercion applies broadly to any individual or entity that seeks to prevent an individual from exercising his or her rights or to retaliate against him or her for having exercised those rights ... Any form of retaliation or coercion, including threats, intimidation, or interference, is prohibited if it is intended to interfere."
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.
What do you want your website to look like? Consider websites that are similar to the one you’d like to build, ideally in the same industry or serving similar types of customers. Build a set of examples of types of pages, design aspects, and website features that you can hand off to the web designer — the person you hire should have experience creating websites with the features you want. If they don’t have the right skill set, they’re not the right pro for you.
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.
One of the first major ADA lawsuits, Paralyzed Veterans of America v. Ellerbe Becket Architects and Engineers (PVA 1996) was focused on the wheelchair accessibility of a stadium project that was still in the design phase, MCI Center (now known as Capital One Arena) in Washington, D.C. Previous to this case, which was filed only five years after the ADA was passed, the DOJ was unable or unwilling to provide clarification on the distribution requirements for accessible wheelchair locations in large assembly spaces. While Section 4.33.3 of ADAAG makes reference to lines of sight, no specific reference is made to seeing over standing patrons. The MCI Center, designed by Ellerbe Becket Architects & Engineers, was designed with too few wheelchair and companion seats, and the ones that were included did not provide sight lines that would enable the wheelchair user to view the playing area while the spectators in front of them were standing. This case and another related case established precedent on seat distribution and sight lines issues for ADA enforcement that continues to present day.
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).