Video remote interpreting (VRI) is a fee-based service that uses video conferencing technology to access an off-site interpreter to provide real-time sign language or oral interpreting services for conversations between hearing people and people who are deaf or have hearing loss. The new regulations give covered entities the choice of using VRI or on-site interpreters in situations where either would be effective. VRI can be especially useful in rural areas where on-site interpreters may be difficult to obtain. Additionally, there may be some cost advantages in using VRI in certain circumstances. However, VRI will not be effective in all circumstances. For example, it will not be effective if the person who needs the interpreter has difficulty seeing the screen (either because of vision loss or because he or she cannot be properly positioned to see the screen, because of an injury or other condition). In these circumstances, an on-site interpreter may be required.
Regarding examples of accessible websites, I would suggest the Accessiweb gallery: http://www.accessiweb.org/index.php/galerie.html. Accessiweb is a reference list 100% based on WCAG2, and they deliver quality marks (the "Accessiweb label") upon website owners solicitation. The website undergoes a thorough manual review (on a carefully defined 10-page sample, more or less), and it gets the label only if it's flawless on every page. The level is reflective of the number of defects found and not corrected. Bronze is exactly equivalent to level A, Silver to AA, and Gold to AAA. So getting a Silver label means all A and AA tests were passed on all of the sample. Bronze, two stars: All A tests were passed, plus 50 to 75% AA tests. And so on.
@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.
Enough Time: Users have sufficient time to read and use the website’s content. If part of the website has a time limit, users are able to turn off the time limit, or they can adjust or extend it to at least ten times the default limit (unless the time limit is essential to the website’s functionality, such as auction websites like eBay). Content that moves, blinks, or automatically updates can be paused or stopped unless it’s essential to the website’s functionality.
UPDATE: Since writing this post in August 2017, several important changes have taken place in the laws regarding ADA compliance for websites. On December 26, 2017, the Department of Justice announced that they have withdrawn the Obama-era Advance Notice of Proposed Rulemaking mentioned in this article which intended to require ADA website compliance. The DOJ’s withdrawal announcement stated, “The Department will continue to assess whether specific technical standards are necessary and appropriate to assist covered entities with complying with the ADA.”
It isn’t a problem by default, a lot of it comes down to how it is built. I’d suggest either considering a highly accessible contingency option, or build those components in such a way that there is a level of accessibility baked into it. If you need help with that testing or review email us at questions at yokoco.com and we’ll be able to let you know the cost for us to lend a hand.
Legal precedent is changing, and ADA compliance related lawsuits are becoming more successful, and the courts are seeing more of them as a result. Title III of the Americans with Disabilities Act pertains to private sector businesses. Lately, those protections are more frequently expanding into digital territory as web and mobile applications become more necessary in our day-to-day lives.
I think it's a pretty good sample of doubtlessly accessible websites. Of course they have put a special effort in getting this label, but somehow it shows that it's possible. I also like the fact that they are pretty diverse in their purposes and target audiences, and are not visually different than the usual production. Which confirms our claims that accessible does not mean boring or not visually appealing - at least, if it's the case, then blame the designer, not accessibility!
Every year numerous lawsuits are taken against businesses that fail to follow the ADA’s proposed requirements for web accessibility. This failure occurs because organizations, including state and local government entities, fail to read the ADA Best Practices Tool Kit.8 They also do not follow the most up to date version of the WCAG.9 These two failures are not only detrimental to people with disabilities who want to effectively browse the web, but they are also inexcusable in today’s digitally driven world.
In court, Netflix tried to argue that websites should not be part of ADA compliance regulations, as there is no physical structure / location. They also argued that websites should not be in scope of ADA as there is no public component (the original ADA compliance law specifically called out that ADA rules apply primarily to services, locations, and products that are supposed to be open to the public).
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.
You probably won't have to check your site with all of the available evaluation tools out there, but it is a good idea to do so for the most common web browsers. Just as accessibility software makes it easier for people with disabilities to navigate the Internet, these tools make it easier for developers to ensure accessibility from the start. When you think you've mastered it, go back through the Section 508 compliance checklist to ensure you've met every goal.