508 and ADA Compliance

LSVT implements all standard W3C “recommendations” and WCAG 2.0 in web development including the documented principles; Perceivable, Operable, Understandable and Robust, so that industry standard tools (such as screen readers like JAWS) can parse and address content for users that have accessibility needs, as well as Closed Captions can be added to the video training modules. One specific alternative interpretation that we do not implement are extreme “abstractions” such that cover a wider content accessibility for people with specific disabilities, specifically; non-text content available in braille.

What’s the Difference Between ADA Compliance and 508 Compliance?

They’re pretty much the same, really. ADA is the Americans with Disabilities Act, and it refers to making all resources, both physical and digital, accessible to persons with disabilities. There’s no such thing as ADA Compliance when it comes to the web, it’s more about protecting a disabled persons’ civil rights.

508 Compliance by contrast is a set of standards created by the U.S. Government to apply to digital material. Officially, only government websites have to maintain compliance. However, most healthcare organizations and websites targeted to seniors make efforts to maintain compliance.

508 Compliance comes down to just a few core principles:

  • Keyboard vs. Mouse Use: All actions and interactions that a user can take on your site must also be accessible by using the keyboard. This means no mouse rollovers, no hover on commands that aren’t also accessible by using the keyboard only. It’s unclear at this time how this standard will impact swipe and pinch technology on mobile.
  • Providing Text Alternatives: All text that is accessible within images, video, or otherwise must also be available in text form. This is so that a screen reader can access exactly the same information on the page as a visual user. All video or image based content must provide a transcript.
  • Using screen readers: Tools for the visually impaired, like screen readers, must have indications when an interaction with the page is taking place. For example, if a drop down menu opens, the reader must indicate that the menu is open and tell how to close it. If an image is used on the page for something other than simple design, the alternative text associated with that image must describe the image.
  • Selecting contrast and color: You must maintain a highly readable contrast (specific percentages are provided) and any use of color must be defined for the screen reader. Colors must be “web safe” and no CSS commands should change the browser’s native display such that a screen reader cannot translate it.
Updated on February 14, 2020
Need Support?
Can't find the answer you're looking for?
Contact Support