@Rick, I didn't specifically look at doctype, but Steve Faulkner did in his original article (see the link at the top of this post). He found that 101 of the 130 pages containing role="main" (78%) used the HTML5 doctype, which of course leaves 22% that didn't. I do recommend using ARIA even if using an earlier doctype. Validation is important, but if validation and accessibility conflict, I think most would agree accessibility should trump validation. Assistive technologies that support ARIA landmarks do so regardless of doctype, and otherwise the presence of these role attributes has no ill effects in any user agent.
For most people, the Americans with Disabilities Act (ADA) conjures up pictures of physical accommodations such as wheelchair ramps near building entrances, handicapped parking spaces, and the use of braille writing on signs and placards. These measures have been tremendously valuable in helping the 56.7 million Americans with a disability function and thrive within society.
This guidance document is not intended to be a final agency action, has no legally binding effect, and may be rescinded or modified in the Department's complete discretion, in accordance with applicable laws. The Department's guidance documents, including this guidance, do not establish legally enforceable responsibilities beyond what is required by the terms of the applicable statutes, regulations, or binding judicial precedent.
The Federal Communications Commission (FCC) enforces regulations covering telecommunication services. Title IV of the ADA covers telephone and television access for people with hearing and speech disabilities. It requires telephone and Internet companies to provide a nationwide system of telecommunications relay services that allow people with hearing and speech disabilities to communicate over the telephone.
Reha asked Vu if companies are obligated to comply? Vu said that unlike the physical access world, where any new building has to be compliant no matter what, there’s no such thing in the web world. The Justice Dept. hasn’t said that that’s the default, but they have said that the current regulatory regime requires it anyway. Equal access has been around since 1990.
For discussion’s sake – while I don’t know the specific nature of your videos, my guess is that they might be demonstrating various techniques or other content in which simply hearing the audio of the video wouldn’t deliver the full context of the content. If making that content accessible is something you’d want to do, you’d likely want to start with a written description of what takes place in the video. Beyond that, high contrast vector images or diagrams showcasing specific parts of the technique would certainly help.
Title III of the Americans with Disabilities Act (ADA) requires that businesses and nonprofit services 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.