- From: Shawn Henry <shawn@w3.org>
- Date: Fri, 9 Aug 2019 10:57:43 -0500
- To: sduchateau@access42.net
- Cc: wai-eo-editors@w3.org
Thank you so much, Sylvie! I appreciate your taking the time to go through the resource before your holiday. I fixed all the wording mistakes. I created a GitHub issue on the sign languages question: https://github.com/w3c/wai-media-guide/issues/88 Best, Shawn On 8/9/2019 9:34 AM, Sylvie Duchateau wrote: > Hello Shawn, > > Here are a few comments on last draft of making audio and video media accessible. > > 1. Audio description page: https://wai-media-guide.netlify.com/design-develop/media/description/ > In "Tips for Recording Descriptions", typo: "Use a neutral voice that does nto convey emotions." > > > 2. Captions page: > > https://wai-media-guide.netlify.com/design-develop/media/captions/ > In Caption Tools: > This sentence is not clear : "Most caption-editing tools provide can export a plain text transcript." > Two verbs? > > > 3. In page transcripts: https://wai-media-guide.netlify.com/design-develop/media/transcripts/ > > In "does my media need a transcript"? There seems to be one word that should be deleted: "In a some cases, transcripts are not required to meet WCAG standards." > > > 4. In page Sign languages: https://wai-media-guide.netlify.com/design-develop/media/sign-languages/ > > "Sign language is not required by most policies. > Sign language is in the WCAG standard at Level AAA. " > Shouldn't it be explained why it is not required. Often, deaf people are not satisfied that sign language is not available. > 5. Accessible media players: https://wai-media-guide.netlify.com/design-develop/media/player/ > Typo in, player accessibility functionality: "More details on player accessibility functionalty are in a separate document:" > > > That's all! > > Best and hearing from you in September! > > Sylvie > > > > >
Received on Friday, 9 August 2019 15:57:55 UTC