Title III of the Americans with Disabilities Act (ADA) requires that businesses and nonprofit service providers make accessibility accommodations to enable the disabled public to access the same services as clients who are not disabled. This includes electronic media and web sites. While the ADA applies to businesses with 15 or more employees, even smaller businesses can benefit from ensuring that their websites are ADA compliant. Doing so opens your company up to more potential clients and limits liability. Web developers should include ADA compliant features in the original site and application plans.
This is particularly important when working for a government agency or government contractor as these organizations must follow web accessibility guidelines under Section 508 of the Workforce Rehabilitation Act of 1973. Although ADA and Section 508 compliance are different, the published checklist for Section 508 compliance offers insight into ways to make websites accessible for people with disabilities, and thereby works toward ADA compliance.
To check your website for accessibility, use the accessibility checklist published by the U.S. Department of Health and Human Services (1194.22 Web-based intranet and internet information and applications):
- Every image, video file, audio file, plug-in, etc. has an alt tag.
- Complex graphics are accompanied by detailed text descriptions.
- The alt descriptions describe the purpose of the objects.
- If an image is also used as a link, make sure the alt tag describes the graphic and the link destination.
- Decorative graphics with no other function have empty alt descriptions (alt= “”).
- Add captions to videos.
- Add audio descriptions.
- Create text transcripts.
- Create a link to the video rather than embedding it into web pages.
- Add a link to the media player download.
- Add an additional link to the text transcript.
- The page should provide alternative links to the Image Map.
tags must contain an alt attribute.
- Data tables have the column and row headers appropriately identified (using the
- Tables used strictly for layout purposes do NOT have header rows or columns.
- Table cells are associated with the appropriate headers (e.g. with the id, headers, scope and/or axis HTML attributes).
- Make sure the page does not contain repeatedly flashing images.
- Check to make sure the page does not contain a strobe effect.
- A link is provided to a disability-accessible page where the plug-in can be downloaded.
- All Java applets, scripts and plug-ins (including Acrobat PDF files and PowerPoint files, etc.) and the content within them are accessible to assistive technologies, or else an alternative means of accessing equivalent content is provided.
- When form controls are text input fields, use the LABEL element.
- When text is not available, use the title attribute.
- Include any special instructions within field labels.
- Make sure that form fields are in a logical tab order.
- Include a ‘Skip Navigation’ button to help those using text readers.
(Courtesy U.S. Department of Health and Human Services)
If the site meets all these criteria, it is likely accessible to people with disabilities. The best test is to obtain feedback on the site’s ease of use from people who are blind, deaf, and have mobility disabilities, then address their feedback with site improvements.
When collecting feedback, ask users what type of adaptive technologies they use. This will allow you to cater your website to your particular clientele and will help you allocate resources toward the best compliance options. Navigating the Internet is particularly challenging for people with limited or no vision. Many blind people use specialized web browsers and software that works with standard web browsers like Internet Explorer. These specialized tools have features that enable users to maximize their Internet use and experience. This screen-reading software reads the HTML code for websites and gives the user a verbal translation of what is on screen.