W3C

Site Navigation

Nearby

Results of Questionnaire EOWG review AV Media Resource - 19 June version

The results of this questionnaire are available to anybody. In addition, answers are sent to the following email address: shawn@w3.org

This questionnaire was open from 2019-06-19 to 2019-06-28.

8 answers have been received.

Jump to results for question:

  1. Resource pages ready for your review.
  2. Review level and timing
  3. Intro Page
  4. Planning Accessible Audio and Video Media
  5. Accessible Audio and Video Content
  6. Audio Description of Visual Information
  7. Captions/Subtitles
  8. Sign Languages page
  9. Accessible Media Players
  10. Sign Languages - How to Cover?

1. Resource pages ready for your review.

You can use this survey to put your input:

  • for the editor
  • for potential discussion at the 21 June teleconference

You're also welcome to open new GitHub issues instead of putting comments in this survey.

All but one of the pages is ready for review:

  1. Making Audio and Video Media Accessible - Introduction
  2. Planning Media Accessibility
  3. Video and Audio Content
  4. Audio Description of Visual Information
  5. Captions/Subtitles
  6. Transcripts (not ready for review)
  7. Sign Languages
  8. Accessible Media Player

And a few other things yet to be done:

Also, there is a specific issue for your input in the Sign Languages - How to Cover? question at the end of this survey.

Focus for your review:

  • Are all topics covered well? Is anything missing? Is anything in there that shouldn't be?
  • Try to note any significant issues at this point, so we can address them now.
  • Comments on details, including wording, are welcome at this point.
    (There are a couple of @@s. You don't need to point them out. You are welcome to provide information to fill them in.:-)

Background: The project page includes use case examples, user tasks, etc.

Details

Responder Comments
Lewis Phillips
Brent Bakken
Sylvie Duchateau
Eric Eggert I have to abstain, 1.5 work days to review 7 pages was just not workable with my other commitments.
Laura Keen I'm unable to give this resource attention this week. I was away for 7 days and am trying to catch up with my Library work. I will have more time next week.
Estella Oncins Scenario / Use Case Examples
[in-house audiovisual department and outsourcing accessibility services]
This is an example based in a real UC. We had a meeting with the contemporary art museum in Barcelona. They hold conferences cycles, live stream them, record them and post them in their webpage (in-house department). Live events are not accessible and most of the videos in their webpage (youtube channel do not include subtitles/cations or audio description). They always outsource the accessibility of their videos but have their in-house production.
This is the case of most public administrations at least in Spain and I guess in Europe, I don't know about other countries. Since the Accessibility Act has been approved and enters into force today, public administrations in Europe are facing a major challenge in the next years, which has to be addressed and I think that it is worth to consider this UC.
Jennifer Chadwick The topics are covered well - there is a clear explanation of what things are, why and how they impact each user and
Vicki Menezes Miller I need more time. Have done a couple of the pages but I would need until Wednesday, June 26th to complete.

2. Review level and timing

Please indicate below the level of consideration you were able to provide for this review. If you were unable to get to it and would like more time, please indicate that as well. Thanks!

Summary

ChoiceAll responders
Results
I read the material carefully . 2
I skimmed the material
I need more time and have put a date below when I can get to it.
I am not going to be able to review this material and will defer to the decisions of the group.

(6 responses didn't contain an answer to this question)

Details

Responder Review level and timing
Lewis Phillips
Brent Bakken
Sylvie Duchateau
Eric Eggert
Laura Keen
Estella Oncins I read the material carefully .
Jennifer Chadwick I read the material carefully . I started with the first page and used the "next" button to move through the content in order from the parent page (Audio & Video Media) to each sub-page (Planning, etc.). To me, this works well to align with the mental model of someone who is learning about a topic (accessible media) for the first time and as a consultant or trainer, I would advise the student or learner to walk through the whole section step-by-step, carefully. This helps provide a step-by-step introduction to the what, why and how.
Vicki Menezes Miller

3. Intro Page

Making Audio and Video Media Accessible - Introduction

Changes from previous version:

Any discomfort with this change?

Other comments on this page:

Details

Responder Intro Page
Lewis Phillips
Brent Bakken Not sure I like the change of the links. It seems that now someone will begin going through the introduction page and then start immediately going to the other pages instead of reading through the intro page because the links come before the explanation of what to do to make media accessible, and then lead them to the planning page. I know that they don't HAVE to go through the resource in order, but this could unintentionally lead them off to other pages in different orders very quickly. The previous version at least had the links after the explanation of the "elements," and they were in order of the navigation as well. The new version is in a different order.

The revised "making audio and video media accessible" section is good. I like that change.
Sylvie Duchateau Suggestion : the summary only talks about media. Add a sentence explaining what is meant under media?

concerning sign language, although they are native language for many people, others do not understand it because they did not have the opportunity to learn. Is it worth mentionning it in this intro?
Regarding media player, what about saying that viewing captions can also be set : change font size, or other display of captions?
IN "an captions can be", I don't understand last bullet: "Used to better understand content since users can hear the information in audio and see it in text at the same time. For example, {some data like this}.
Eric Eggert
Laura Keen
Estella Oncins Excellent page no comments.
Secondary comment: I would suggest "Understanding User Needs" instead of "Understanding User Experiences"
Jennifer Chadwick No comments other than the page structure and content are clear, concise and easily digestible.

I like how the important goals or points are in bold text. If a sighted user, it helps me quickly scan the page to identify the purpose of the section or page so I know I'm not wasting my time. Also having the different disability types in bold - "Deaf", "difficulty processing information" etc. - draws my attention to that section which should not be overlooked.
Vicki Menezes Miller First sentence: "This Web Accessibility Initiative (WAI) resource helps you make your media:"
Maybe add in brackets what media generally covers.

Sentence: "Descriptive transcripts also include visual information needed to understand the content. "
As I read this, I feel that some further clarification is necessary. My understanding is that a description of the visual information is included in descriptive transcripts. I would modify slightly the sentence to "Descriptive transcripts also include an explanation of the visual information needed to understand the content."

Editorial suggestion: (mid-way), bullet point "the Web Content Accessibility Guidelines (WCAG) standards for audio and video media", suggested change: "provides guidance on the Web Content Accessibility Guidelines (WCAG) standards for audio and video media".

Suggestion in structure. I would move the heading "Making Audio and Video Media Accessible" to after additional benefits since it seems more logical to me to group the benefits in one place and then move to talking about how to make audio and video media accessible.

Editorial suggestion: under heading "Example". "An example accessible video is Video Captions. That page provides:"
Suggested change: "An example accessible video is available on the page Video on Captions, which provides:"

Editorial suggestion: under heading "Additional Benefits",

- bullet point "Used in loud environments where users cannot hear the audio. For example, a bar, an airport, and another."
Text is incomplete, suggestion "Used in loud environments where users cannot hear the audio. For example, a bar, an airport, and other such situations where surrounding noise hinders audio comprehension".
- bullet point "Used in quiet environments where users cannot turn on sound. For example, a library, when others are sleeping, and another."
Text is incomplete, suggestion "Used in quiet environments where users cannot turn on sound. For example, a library, when others are sleeping, and another similar situations."

4. Planning Accessible Audio and Video Media

Planning Accessible Audio and Video Media

Comments on this page:

Details

Responder Planning Accessible Audio and Video Media
Lewis Phillips
Brent Bakken - Typo - close parenthesis around WCAG in the summary box

- In the "What does my video need to be accessible?" section, I would switch the order of the check boxes for "Audio description of the visual information" and "Descriptive transcript" to match the order of WCAG SCs 1.2.3 and 1.2.5.

- Question: Is there ever a video that there is NO visual information that needs to be understood? If no, then do we need "If no, inform users."? Maybe I just need to hear about some examples of videos that would have this exception.

- In the "Live Video" section under speech and other audio. Without an exact transcript supplied before hand, you will not be able to have "text synchronized with the audio" when providing live captioning. There will always be a delay. I think this needs some slight rewording.

- In the "Live Video" section under visual information. How can you have a "Descriptive transcript that provides the audio and video information to people who are Deaf-blind." for live video. You do not know exactly what will be in a live video until it is happening most of the time. For example, a presidential speech, they can provide the speech as a transcript prior, but not a description of what is in the video feed. They would not know when the camera is going to break away from the president and show angry audience members due to something that was said. I think this only applies in the pre-recorded Success Criteria 1.2.3 and 1.2.5 NOT in 1.2.4 of which this is referring to.

- I really like the section "Both Captions and a Transcript"
Sylvie Duchateau 1. In "What does my audio-only (e.g., podcast) need to be accessible?", "Pre-recorded audio:"
I don't understand the first bullet: "Audio content that works for people who cannot hear well or cannot see."
Why people who cannot see?
I also don't understand where the links in these bullets lead to, the introduction page?
2. Same question for live audio
3. I don't understand, why in some bullets one can read "ideally" and why not in others.

4. In pre recorded video:
The question to answer is not clear:
"Is there speech or other audio that is needed to understand the content?"
Suggestion: is additional audio information needed to understand the content?
5. Same suggestion for "Is there visual information that is needed to understand the content?"
Suggestion: Is additional visual information needed to understand the content.
Eric Eggert
Laura Keen
Estella Oncins Under checklists pictograms would be useful and more navigation friendly.
Jennifer Chadwick - To me, "Planning" includes action items I can take away to implement in my team, and the checklist is a perfect example of the kind of resource teams are looking for to get started. Thus, this is appropriate for a Planning page.

- I like that, for the bullet point under Checklist about meeting user needs, there is a mention that doing this work goes beyond just compliance. "(including what goes beyond minimum accessibility standards and policies)"

- I like that the WCAG Level is included in each of the components under each type of media. i.e. Audio-only content lists "Audio content (A)" and then "Transcript (A)". This is MUCH EASIER than directing people to the current WCAG listings under Perceivable.

- The way the checklists are structured to gather all of the items, and clearly outline everything that you need to consider when creating a piece of media - is very helpful and clear.

- I really like - and would like to keep - the way the page begins with user need, then planning your checklist of items, then which responsibilities are involved, and then the WCAG requirements are last.
Vicki Menezes Miller Editorial suggestion to the first question "What does my audio-only (e.g., podcast) need to be accessible?"
A possible suggestion: "What needs to be done to make my audio-only (e.g., podcast) resource accessible?

Editorial suggestions to the bullet points following the above question: remove "that" in each case, e.g.
- Audio content that works for people who cannot hear well or cannot see.
change to
- Audio content works for people who cannot hear well or cannot see.

The headings which follow also use "that" in each case. For skimming, it seems better and more assertive to remove the "that".

Editorial suggestion to heading "Informing Users When None Needed". Suggested change "Inform your users when captions are not required".

Editorial suggestion to heading "Both Captions and a Transcript". Suggested change "Using both captions and transcripts".
Editorial suggestion to sentence "Ideally you provide captions and a separate transcript." Suggested change "Ideally, you should provide captions and a separate transcript."

Editorial suggestion under heading "Workflow and responsibilities", sentence "By: The same people doing the main video also do the describe version." Suggested change: "By: The same people preparing the main video should also provide the descriptive version."

5. Accessible Audio and Video Content

Planning Accessible Audio and Video Media

Any additional guidance to include?

Comments on this page:

Details

Responder Accessible Audio and Video Content
Lewis Phillips
Brent Bakken This page is excellent. I really like it. Only one typo...

In the "Time for Description" section...
"For some types of videos, the description of the visual information cannot be smoothly handled by the speakers and narrator in the main video, because it would make the default video [[too much longer]] or more cumbersome." --> Change to "much to long..."
Sylvie Duchateau No additional comments
Eric Eggert
Laura Keen
Estella Oncins I really like the page, but I would include some recommendations in the description of each title in order to consider the different agents in the audiovisual chain. Most of the times the people that will use these resources are not the speakers but the technicians and producers or event managers.
For instance, under "Audio" > speak clearly > If you are recording a conference give the speaker the following recommendations...
Jennifer Chadwick - This page is easily digestible, provides clear instructions and best practices that can be applied to someone's next project or easily shared in an internal training session.
Vicki Menezes Miller Very good and clear. Minor comment on one heading:

Heading "Time for description"
Comment: Minor suggestions. Please see suggested changes.

"Time for description
For some types of videos, the description of the visual information cannot be smoothly handled by the speakers and narrator in the main video, because it would make the default video too much longer or more cumbersome. In that case, you will have the description separate. You can make the described version smoother by planning for the description.

Where the description is fairly short, plan space in the audio for the description.

Where the description is longer that you want to leave space in the main audio, you can record extra time in the scene to accommodate the description without having to pause the scene. That is, the same scene is shown with a little longer at the beginning or the end of it. For example:

Instead of "In that case, you will have the description separate. You can make the described version smoother by planning for the description."
Suggested change: "In that case, you will need to have the description separate and planning for the description video will make the described version better."

Instead of "Where the description is fairly short, plan space in the audio for the description."
Suggested change: "Where the description is fairly short, plan space in the audio for the description version."

This sentence is not too clear. "Where the description is longer that you want to leave space in the main audio, you can record extra time in the scene to accommodate the description without having to pause the scene. That is, the same scene is shown with a little longer at the beginning or the end of it. "

6. Audio Description of Visual Information

Audio Description of Visual Information

Comments on this page:

Details

Responder Audio Description of Visual Information
Lewis Phillips
Brent Bakken - In the Terminology section. The word "areas" in the following sentence is ambiguous until you read, "such as Canada."
"Audio description is called “described video” in some areas, such as Canada." Would be better to say, "Audio description is called “described video” in some [countries ~or~ geographies], such as Canada." I initially interpreted the beginning of that sentence like the one below it.

- Missing a close parenthesis in the first paragraph of "Creating a Separate Described Video - If Descriptions Do Not Fit in Spaces" section.



Sylvie Duchateau 1. In the section who needs audio description: people who can benefit from audio description are also people who have learning disabilities and do not understand the video.

2. Suggestion: add somewhere in the document that unnecessary information should not be included in the audio description. For example: Someone opens a door, the audio description says : "X opens the door". This description is not necessary if you hear the noise of the door opening.
In addition, you could add following tip: ask users. People who cannot see the video can give you information about what they need to understand the video, what is missing and what is not necessary to describe.

3. For videos that do not have enough spaces to add all audio descripted information, it may be necessary to modify the visual trak as well, as you state in the document. Consider adding information about the case where the video is not your property and you need author's authorisation.
4. In tips for recording descriptions, may be add that the volume of the descriptive voie should overwhelm the other sounds of the video, ensure that the descriptive voice is neutral.
Eric Eggert
Laura Keen
Estella Oncins Excellent page no comments
Jennifer Chadwick - It may be optional now, but I would like to see a few images added with descriptions of people experiencing the benefits. This is great. Please keep as is.
- I like the format of Who, What and Example. Please keep!
- Very important to include the example of the standard VTT format. It makes me feel I could lift this example and start using it or sharing it with my team.
Vicki Menezes Miller Excellent resource. Very helpful and well put together.
One really minor comment: activate the link under "Other": https://www.w3.org/TR/WCAG20-TECHS/H96.html)

7. Captions/Subtitles

Captions/Subtitles

Comments on this page:

Details

Responder Captions/Subtitles
Lewis Phillips
Brent Bakken - Simple Typo in Live Captions section: "[[This]] rest of this page addresses developing captions for pre-recorded media." Change to "The"

- Omitted word in Does My Media Need Captions section: "Captions are useful for [[ ]] who are hard of hearing to get the richness of listening to the audio and fill in what they don’t hear well by reading the captions." Add the word "people".

- The second half of this page needs some polishing and possibly some revision. This needs to be reviewed more thoroughly.

Sylvie Duchateau 1. Suggestion on structure: I wonder if it would be better to first talk about the difference between captions and subtitles and then, explain what captions are and who benefits from captions.

2. In "Does My Media Need Captions?"
May be the first sentence can be confusing as it says: "Captions are not required. (Your audio content is provided in a transcript.)"
So people may think they do not need to add captions to a podcast.
It is confusing because the bullet after says: "Captions are useful for who are hard of hearing to get the richness of listening to the audio and fill in what they don’t hear well by reading the captions."
3. In automatic-generated captions, may add that auomatic captions may be sometimes confusing wrong words are transcribed. Especially for specific terms like WCAG which may not be recongised correctly.

Eric Eggert
Laura Keen
Estella Oncins I maybe would add some practical recommendations under Caption/Subtitles.
Font (use sans-serif font), size of the letter, use of background, contrast, number of characters per line?
Some further recommendations:
https://easy-to-read.eu/wp-content/uploads/2014/12/EN_Information_for_all.pdf
Jennifer Chadwick - Good, clear and contextual introduction of terms like CART, open and closed captions.
- Visuals / images are good to include here. Please keep.
- I like how this aligns with the mental modal of "what do I need?" … so the section "Does my video need captions" is helpful.
- Like how addressing auto captions and their use is included.
Vicki Menezes Miller Clear

8. Sign Languages page

Sign Languages

Comments on this page? What about not having a summary and sub-headings on this page?

Details

Responder Sign Languages page
Lewis Phillips For the amount of the current content it is ok to not have a summary and sub-headings. If more content is added later that might change. A picture of someone signing would be good, a short video may be better.

Even though adding sign language is optional, it would be nice to cover how it would be added to a page with audio, or embedded into a video.
Brent Bakken Provide notes or tips on sign language production processes. Something similar to the captioning page when talking about outsourcing to a vendor.
Sylvie Duchateau Adding that not all deaf people learned sign language?
Otherwise, ok as is.
Eric Eggert
Laura Keen
Estella Oncins If I read the sentence "Sign language is not required to meet most minimum accessibility standards" I would not include sign language
As mentioned in the last Friday meeting, maybe it can be reformulated in a more recommendation way. "Sign language is not required to meet most minimum accessibility standards but in some countries Sign Language is included in the legislation check"
Jennifer Chadwick - definitely would like to see a demonstration of sign language in an image or video if possible.
Vicki Menezes Miller

9. Accessible Media Players

Accessible Media Players

Comments on this page:

Details

Responder Accessible Media Players
Lewis Phillips
Brent Bakken Provide basic information on options of how to embed media players in various types of pages, content/learning management systems, and applications. Also code samples on how to stream out embedded media files with caption files.
Just seems like we could provide just a little more coding guidance on the page rather then send them off to another site.
Sylvie Duchateau 1. IN "Media Player Support for Accessibility"
"Accessible media players provide a user interface that works without a keyboard, through speech interface, and by screen reader users. They audio description, captions, and transcripts. "
Suggestion: Accessible media players provide a user interface that works with a mouse, a keyboard, through speech interface, and by screen reader users."
Rationale: the user must be able to use it with or without keyboard, with speech input and with a screen reader.
2. In the next sentence it seems that a wor is missing: " They audio description, captions, and transcripts."
They handle?

3. What about talking about the ability in a media player to change volume, speed, navigate through the media, modify captions font size, spacing, font?
Eric Eggert
Laura Keen
Estella Oncins Maybe include some image indicating the position of each accessibility service in the media player menu
Jennifer Chadwick - this is a good resource. Small thing but a lot of people I work with don't know or understand what an "API" is - can we expand on that?
Vicki Menezes Miller

10. Sign Languages - How to Cover?

How do we handle that sign language is suggested, yet realistically, it's not feasible in many situations?
Current draft has for your consideration:

  1. In Elements:
    "(Sign language is not required to meet most minimum accessibility standards.)"
  2. In Planning Accessible Audio and Video Media, under "What does my audio-only (e.g., podcast) need to be accessible?" and "What does my video need to be accessible?":
    "Ideally, Sign language(s) that provides the audio information."
  3. In Planning Accessible Audio and Video Media, under "Workflow and Responsibilities"
    [not included at all...]

Details

Responder Sign Languages - How to Cover?
Lewis Phillips
Brent Bakken Will wait for meeting to hear more about this issue and enter the discussion.
Sylvie Duchateau I tried to write some explanations that need to be improved:
"Sign language is, like every language, a language that needs to be learned. Although there are avatars that simulate sign language interpretation, face expressions, that are essential to understand things in sign language, are not rendered correctly and thus cannot be easily understood by deaf people who use sign language.
As each organisation does not have a sign language speaker, it may be difficult to get media content translated in that language.
As far as implementation of sign language is concerned, media producers must be able to synchronise sign language with the audio of the video.
As these skills are often not available in one organisation, sign language is not required to meet most minimum accessibility standards."
Eric Eggert
Laura Keen
Estella Oncins
Jennifer Chadwick - Basically, include it and share its importance and value. In the same way that I feel AAA is introduced and defined - it is an ideal if it can be done... keep it as a standard to strive to when it is feasible, but also acknowledge that captions can provide for the same need.
Vicki Menezes Miller

More details on responses

  • Lewis Phillips: last responded on 20, June 2019 at 21:17 (UTC)
  • Brent Bakken: last responded on 20, June 2019 at 23:51 (UTC)
  • Sylvie Duchateau: last responded on 21, June 2019 at 08:50 (UTC)
  • Eric Eggert: last responded on 21, June 2019 at 10:40 (UTC)
  • Laura Keen: last responded on 26, June 2019 at 17:24 (UTC)
  • Estella Oncins: last responded on 27, June 2019 at 07:41 (UTC)
  • Jennifer Chadwick: last responded on 27, June 2019 at 21:26 (UTC)
  • Vicki Menezes Miller: last responded on 28, June 2019 at 07:52 (UTC)

Non-responders

The following persons have not answered the questionnaire:

  1. Eric Velleman
  2. Andrew Arch
  3. Shawn Lawton Henry
  4. Shadi Abou-Zahra
  5. Kazuhito Kidachi
  6. Sharron Rush
  7. Jedi Lin
  8. David Sloan
  9. Mary Jo Mueller
  10. Reinaldo Ferraz
  11. Bill Kasdorf
  12. Cristina Mussinelli
  13. Kevin White
  14. Kevin Rydberg
  15. Ahmath Bamba MBACKE
  16. Adina Halter
  17. Denis Boudreau
  18. Sarah Pulis
  19. Bill Tyler
  20. Gregorio Pellegrino
  21. Ruoxi Ran
  22. Sean Kelly
  23. Muhammad Saleem
  24. Sarah Lewthwaite
  25. Daniel Montalvo
  26. Mark Palmer
  27. Jade Matos Carew
  28. Sonsoles López Pernas
  29. Greta Krafsig
  30. Jason McKee
  31. Jayne Schurick
  32. Billie Johnston
  33. Michele Williams
  34. Shikha Nikhil Dwivedi
  35. Brian Elton
  36. Julianna Rowsell
  37. Tabitha Mahoney
  38. Fred Edora
  39. Rabab Gomaa
  40. Marcelo Paiva
  41. Eloisa Guerrero
  42. Leonard Beasley
  43. Frankie Wolf
  44. Supriya Makude
  45. Aleksandar Cindrikj
  46. Angela Young

Send an email to all the non-responders.

Compact view of the results / list of email addresses of the responders

WBS home / Questionnaires / WG questionnaires / Answer this questionnaire

Report issues on GitHub project w3c/wbs-design or by mail to sysreq.