1. Sources
1.1. ADA Best Practices Tool Kit for State and Local Governments
1.2. 5 Steps to Make Sure Your Website Is ADA-Compliant
2. What is ADA?
2.1. Americans With Disabilities Act
2.1.1. prohibits discrimination against people with disabilities in all public areas
2.2. Public ADA Compliant Examples
2.2.1. Auto-opening doors
2.2.2. Wheel-chair ramps
2.2.3. Braille on Door labels
3. Computers & ADA
3.1. Web Content Accessibility Guidelines (WCAG 2.1)
3.1.1. Examples
3.1.1.1. site must be fully navigable via keyboard only
3.1.1.2. site should be navigable with screen reader software
3.1.1.3. site must handle text scaling up to 200% without horizontal scrolling or content-breaking layout
3.2. Site should be accessible for all digital devices
3.2.1. laptop
3.2.2. desktop
3.2.3. tablets
3.2.4. mobile phones
4. Site Accessibility TestTools
4.1. Manual Testing
4.1.1. screen reader software
4.1.1.1. computer program that speaks written text.
4.2. Automated Testing Software
4.2.1. Lighthouse
4.2.1.1. Google Automated tool for improving quality of web pages
4.2.1.1.1. can run it against any web page, public or requiring authentication
4.2.1.1.2. Can audit performance, accessibility, progressive web apps, and more.
4.2.1.1.3. How to Use
4.2.2. Wave Web Accessibility Eval
4.2.3. aXe - Deque
4.3. keyboard only navigation
5. Common Problems/Solutions with Website Accessibility
5.1. Images Without Text Equivalents
5.1.1. Why Problem?
5.1.1.1. Tools like screen readers & refreshable Braille displays can read text.
5.1.1.1.1. They cannot translate images into speech or Braille, even if words appear in the images
5.1.2. Solution
5.1.2.1. Add HTML code to provide text for each image and graphic.
5.1.2.1.1. examples
5.2. Documents Not Posted In an Accessible Format
5.2.1. Why Problem?
5.2.1.1. Image based format documents like PDF often not accessible to people using:
5.2.1.1.1. screen readers
5.2.1.1.2. text enlargement programs
5.2.1.1.3. different color/font settings to read computer displays.
5.2.2. Solution
5.2.2.1. Also provide alternative text-based format documents, like HTML or RTF (Rich Text Format), in addition to PDF.
5.3. Specifying Colors and Font Sizes
5.3.1. Why Problem?
5.3.1.1. Some sites designed so that changing color and font settings is impossible.
5.3.1.2. low-vision users need ability to manipulate color/font settings in browsers/operating systems to make pages readable.
5.3.2. Solution
5.3.2.1. Design sites so Low-vision users can specify text/background colors/font sizes needed to see page content.
5.4. Videos/Other Multimedia Lack Accessible Features
5.4.1. Why Problem?
5.4.1.1. Deaf/hard of hearing individuals may not be able to hear the audio track of a video.
5.4.1.2. People who are blind/low vision may struggle viewing video images
5.4.2. Solution
5.4.2.1. Add Closed-captioned for hearing impaired
5.4.2.2. Provide audio descriptions of images (i.e. changes in setting, gestures, and other details) for vision-impaired