'Media Resource - Publication Approval' survey replies

Hi, Jenn,

Thanks much for your review and comments on the media resource for publication!

Replies are below.
  
> • level: [ED- low]
> • location: Page: “Making Audio and Video accessible”.  Section:
> “Page Contents”
> • https://wai-media-guide.netlify.com/design-develop/media/
> • current wording: "First, Understand User Needs"
> • suggested revision: "Start with Understanding User Needs"
> • rationale: The titles of the sections start with one that is "First,
> …" and the rest don't follow suit (none are labelled Second... Third...
> etc.). A silly small point, but maybe a suggested edit to "First" would be
> to remove it, or change to "Start with Understanding User Needs" … but
> the others are not action-driven.  Not a big deal!

I see your point, and considered the edit. I think "First, Understand User Needs" is more direct and much simpler wording than "Start with Understanding User Needs". And indeed, we want this heading to be imperative, even though the others are not.

I think I'll leave it. :-)

  
> • level: [ED-low]
> • location: Page: “Making Audio and Video accessible”.  Section:
> “How to make Audio and Video Accessible”
> • https://wai-media-guide.netlify.com/design-develop/media/#how-to-make-audio-and-video-accessible
> • current wording: “To figure out which accessibility aspects your
> specific audio or video needs, for project management guidance, and to
> learn about standards, see Planning Audio and Video Media.”
> • suggested revision: “To figure out which accessibility aspects your
> specific audio or video needs, for project management guidance, and to
> learn about *WCAG* standards…”
> • rationale: Many people who have been tasked with working with
> accessibility will be driven by the law and what is required for WCAG.
> This is mentioned briefly under How to Make Audio and Video Accessible, and
> there is a link to the Planning page.  Small change, but since the four
> main sections don't have WCAG in the titles,  I could see some people
> skimming the page for this.  Could this line be changed to include the word
> "WCAG" before “standards”?

Done. I had to write out Web Content Accessibility Guidelines (WCAG) since that's the first use of the acronym on the page.


> • level: [ED-med]
> • location: “Making Audio and Video accessible”.  Section: “How to
> Make Audio and Video Accessible” in “Audio Description of Visual
> Information"
> • https://wai-media-guide.netlify.com/design-develop/media/#how-to-make-audio-and-video-accessible
> • current wording: no change to current wording.  Addition only
> • suggested revision: Add 1-2 examples of an audio description
> • rationale: I can see how "Audio Description of Visual Information"
> could benefit from a couple of real-world examples of something that is
> visually described - and the impact of not having that described in the
> moment.  For instance, if the camera cuts to a gun on the table, but the
> main character does not know it is there and/or does not speak about it,
> this is a significant plot point that was only shown visually.  Having the
> AD say "A gun is shown on the table in the other room" is critical to
> understanding what might happen next.   Another simpler example could be
> the description of the doorbell ringing off-camera.

In some previous versions, we had much more information on the intro page in this section. Several in EOWG wanted it cut down significantly, and I supported that.

I added an example to the linked page: https://wai-media-guide.netlify.com/design-develop/media/description/#introduction

I don't like guns, so I didn't use that, and a doorbell ringing is audio info not visual info. ;-)

For a quick fix, I added: "For example, “Pat opens a jewelry box, looks at a diamond engagement ring, and cries”."

Also in that section there is a link to a full video example.

For automatic captions, we have a very illustrative example bad automatic captions: <https://wai-media-guide.netlify.com/design-develop/media/captions/#automatic-captions-are-not-sufficient>

Probably we want to do something like that for description, too.

My creative juices are not flowing right now, and I don't think it's a show-stopper for publication, so I added it as a GitHub issue for later version:
 https://github.com/w3c/wai-media-guide/issues/103



> • level: [ED-med]
> • location: “Making Audio and Video accessible”.  Section: “How to
> Make Audio and Video Accessible” in “Transcripts"
> • https://wai-media-guide.netlify.com/design-develop/media/#how-to-make-audio-and-video-accessible
> • current wording: no change to current wording.  Addition only
> • suggested revision: Add information about the format for transcripts,
> e.g. “Recommend that the transcript is created in HTML format, on a web
> page, instead of a downloadable PDF.” Also e.g. “Transcripts should be
> available adjacent to the video itself on the same page - ideally not
> provided later, in a separate section”.
> • rationale: It might be good to know what kind of format transcripts
> come in, the options.  I know that there are links to more detailed pages,
> but a quick example on this page might help learning immediately.

In some previous versions, we had much more information on the intro page in this section. Several in EOWG wanted it cut down significantly, and I supported that.

The linked page <https://wai-media-guide.netlify.com/design-develop/media/transcripts/> has whole sections (that are listed in the TOC/Page Contents at the top) on:
* Transcript File Format
* Where to Put Transcripts

After "Make it is easy for users to know that a transcript is available and to get to the transcript." I added: "For example, put the transcript itself or a link to the transcript right under the video."

(I think there are many situations where the transcript should not be adjacent to the video -- because other important information needs to be there. For example: https://www.w3.org/WAI/perspective-videos/customizable/ )

---

Let me know if you have any followup ideas.

Best,
~Shawn

Received on Thursday, 29 August 2019 19:36:04 UTC