RE: Sign Language for audio and video on the web

Hi Shawn,



About The Draft Sign Languages Page<https://wai-media-guide.netlify.com/design-develop/media/sign-languages/>



For “Creating Sign Language Alternatives,” I suggest the following.

  *   Provide the capability of turning sign language on/off any time.
  *   Provide the capability to combine signing with closed captioning.
  *   Provide the capability to position the sign language inset.



(The first two are options for my team’s implementation. See http://bit.ly/ASLdemo. I am looking for funding to implement on-demand inset positioning.)



About the “Introduction,” I suggest text that explains relying upon lip reading is insufficient.



About All The Documents



I suggest you add hard-of-hearing such that, for example, “Sign language is the native language of many people are Deaf” becomes “Sign language is the native language of many people who are Deaf or hard-of-hearing”. Millions of people who are not completely deaf, even those using assistive technology, need to communicate via sign language.


John

John Rochford<http://bit.ly/profile-rj>
University of Massachusetts Medical School
Eunice Kennedy Shriver Center
Director, INDEX Program
Faculty, Family Medicine & Community Health
www.DisabilityInfo.org
LinkedIn<https://www.linkedin.com/in/john-rochford/>

Confidentiality Notice:
This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential, proprietary, and privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender immediately and destroy or permanently delete all copies of the original message.


-----Original Message-----
From: Shawn Henry <shawn@w3.org>
Sent: Wednesday, July 24, 2019 2:25 PM
To: Rochford, John <john.rochford@umassmed.edu>
Cc: wai-eo-editors <wai-eo-editors@w3.org>
Subject: Sign Language for audio and video on the web



[CC: wai-eo-editors@w3.org<mailto:wai-eo-editors@w3.org>]



Hi John,



I hope your summer is going well! I have been thankful for air conditioning this summer in Madison. And after over a week of very hot, humid weather, I enjoyed the cool, dry break earlier this week in the Midwest.



Remember I told you about the WAI EOWG resource on including sign language for videos? The draft is now refined enough that it's ready for your review.



First, some background and context:

* The use cases and tasks for the resource are here: <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_WAI_EO_wiki_Accessible-5FMedia-5FResource-23Requirements-5FAnalysis&d=DwICaQ&c=WJBj9sUF1mbpVIAf3biu3CPHX4MeRjY_w4DerPlOmhQ&r=CueeOhb9CA5L2yfl16hThwCe1zS5LdHYD5MikPNgKr4&m=iCd1kg__CyC45TYtV6L9n1IiR6sFVXfBiWWX7fsfHcc&s=1rmswIEUe7Pqt8WMA5gOqjhgUQbtFu-KpAswvw_52lI&e=>

** One particularly relevant for this is: "[advocate] I want to convince XYZ organization to make their media accessible. I want them to realize the importance for people with disabilities and the additional benefits that they get from it (e.g., SEO). *It'd be good if from skimming this resource they feel like it's not a huge task.*"

** The big challenge with sign language is to *encourage* readers to include it, *and* not scare them away from media accessibility all together (e.g., because providing sign language is resource-intensive and beyond many organization's capabilities in-house).

* The intro for the multi-page resource is here: https://urldefense.proofpoint.com/v2/url?u=https-3A__wai-2Dmedia-2Dguide.netlify.com_design-2Ddevelop_media_&d=DwICaQ&c=WJBj9sUF1mbpVIAf3biu3CPHX4MeRjY_w4DerPlOmhQ&r=CueeOhb9CA5L2yfl16hThwCe1zS5LdHYD5MikPNgKr4&m=iCd1kg__CyC45TYtV6L9n1IiR6sFVXfBiWWX7fsfHcc&s=_gkGCJEcRt0t936nD15eStY1CjEqlCQ3A5EkKMoQgPY&e=




And, now [drum-roll] here is the page with most of the sign language information:

      https://urldefense.proofpoint.com/v2/url?u=https-3A__wai-2Dmedia-2Dguide.netlify.com_design-2Ddevelop_media_sign-2Dlanguages_&d=DwICaQ&c=WJBj9sUF1mbpVIAf3biu3CPHX4MeRjY_w4DerPlOmhQ&r=CueeOhb9CA5L2yfl16hThwCe1zS5LdHYD5MikPNgKr4&m=iCd1kg__CyC45TYtV6L9n1IiR6sFVXfBiWWX7fsfHcc&s=JW3wCF1y8IYVNwKVnDwsce6mHhPhy3pgRGpqDOnXMPc&e=




We welcome your input on any of it. Feel free to:

* use GitHub pull requests

* create new GitHub issues (one for each point, please): https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_w3c_wai-2Dmedia-2Dguide_issues_new&d=DwICaQ&c=WJBj9sUF1mbpVIAf3biu3CPHX4MeRjY_w4DerPlOmhQ&r=CueeOhb9CA5L2yfl16hThwCe1zS5LdHYD5MikPNgKr4&m=iCd1kg__CyC45TYtV6L9n1IiR6sFVXfBiWWX7fsfHcc&s=J60OdO9MXAaA56RWqUxAopRXXau1P34qQz4YpXdC1cg&e=


* send e-mail to the publicly-archived list: wai-eo-editors@w3.org<mailto:wai-eo-editors@w3.org>

* e-mail me directly

* talk over the phone



It would be best to get your comments by Thursday 1 August. We can take them later, if needed.



Let me know what questions you have.



Thanks so much for sharing your expertise and perspectives on this!



Warm regards,

~Shawn