Results of Questionnaire ISSUE-142: No alternative text description for video key frame (poster) - Straw Poll for Objections

The results of this questionnaire are available to anybody.

This questionnaire was open from 2011-03-10 to 2011-03-17.

4 answers have been received.

Jump to results for question:

  1. Objections to the Change Proposal for no poster short alternative text
  2. Objections to the Change Proposal to introduce a new child element to the video element.

1. Objections to the Change Proposal for no poster short alternative text

We have a Change Proposal to specify that there is no poster short alternative text. If you have strong objections to adopting this Change Proposal, please state your objections below.

Keep in mind, you must actually state an objection, not merely cite someone else. If you feel that your objection has already been adequately addressed by someone else, then it is not necessary to repeat it.


Responder Objections to the Change Proposal for no poster short alternative text
Laura Carlson What this all boils down to is the ability to access content. If <video poster> provided no content <video poster> would not exist.

This change proposal states: "we provide the possibility of indicating an image which is more indicative of the content". [1]

HTML5 should have a mechanism to provide that indication to people with disabilities. Currently it does not. <firstframe> provides that possibility. It offers a mechanism to equitably obtain that same content currently in <video poster> to people with disabilities.

[1] http://www.w3.org/html/wg/wiki/index.php?title=ChangeProposals/NoPosterAlt&oldid=9214
Kornel Lesinski
Leif Halvard Silli I strongly object. This CP doesn't ensure that unsighted always can be provided access to:

A) sufficient or equal info before deciding to run a video;
B) alternative text for info that sighted get even without running the video;
(Point A) and B) are different sides of same coin.)
C) Also see Comments under C) below.


A) <img>s are consumed instantly (by AT users too). But videos are consumed in 2 steps, where step 2 (running the video) depends on evaluation of
1) costs of running the video (time costs, quality costs/technical limits);
2) perceived benefits (info on the video's subject & "teasers")
PROBLEM 1: Different defaults: The benefits are more diffult to evaluate without a firstframe image than with a firstframe image. But, luckily for sighted, there always *is* a firstframe image even without whether @poster or <firstframe src=*>. Solution: a <firstframe src=* alt=*> with the authoring guidelines John propososes (see his General Principles section: http://www.w3.org/html/wg/wiki/ChangeProposals/PosterElement#General_Principles), helps authors to provide for unsighted what sighted get by default.
PROBLEM 2: Different needs: Just as for <img>, what unsighted need in text format is different from what sighted need in text format. E.g. imagine that the video's firstframe displays text. Solution: <firstframe alt=*> allows authors to take care of the difference.
PROBLEM 3: Same expectations: The firstframe image creates useful expectations about what to see: When starting a video, the exciting scene (or info) on the firstframe image might be preceded by dull footage or advertising. Someone who sees the firstframe image (all the sighted!) or at least read its description, would be less likely to stop playing the video early than someone with minimal clue about what to expect. Solution: <firstframe> allows authors to build up similar expectations within the unsighted audience as within the sighted audience.

B) To a sighted, the firstframe image can have value in itself. Speaking for myself, when news articles contain video I tend to "jump over" them, but I still eagerly consume their firstframe images. Thus, a firstframe image without a description is information-loss for the unsighted. An HTML standard where <img src=ExitingMoment > is covered by @alt and its usage guidelines, but were <video src=VideoWithAnExitingMomentAsTheFirstframeImage > does not have similar possibilities or guidelines, would be a missed opportunity.

C) Comments to certain claims:

C1) CP says: "it should be described as part of the description of the video element itself". But by which feature? <track> is synced with the video file and not with the still picture of the firstframe image. It should be as easy to change the firstframe text as it is to change the firstframe image - one shouldn't need to edit whether a <track> file or a video source file. John's CP also demoes that the firstframe could specify for whom the film is suitable: one should not need to read a longer, general video description to locate this. Plus that some of the firstframe's teaser effects could be lost if the firstframe text is mixed together with a general description of the video.

C2) The CP claims that because the firstframe image is "conceptually part of the media resource itself" it "should be described as part of the description of the video element itself". However, from a different angle, a firstframe image description *would* then be a video description, if but of a detail of it.

C3) The name: <firstframe> at first seemed unoptimal (e.g. because John's CP says that it could be used for <audio>). However, if we ignore <audio> (which has no image feature), and instead consider Sylvia Pfeiffer's point (http://www.w3.org/Bugs/Public/show_bug.cgi?id=10642#c76) that the user don't know whether the image stems from (in John's proposal) <firstframe src> or the movie file, then <firstframe> make very good sense.

C4) CP says that "'poster' is the term commonly used in the industry". May be. But for example such a thing as <param name="poster" value="*"> does not seem to exist for whether QuickTime, MediaPlayer or Flash.

C5) Comment on a poll comment by Philip Jägenstedt: Whether the firstframe image text must accurately reflect the firstframe image or simply be a text that could serve as a useful textual teaser, seems like an authoring guide question. For instance, if the video's firstframe shows what this CP describes as "a fade from black, the green MPAA rating, the roaring lion, etc", then it may not make sense to *require* the firstframe text to reflect this. John's CP says the author in such cases MAY omit <firstframe> (note: <firstframe> always requires @alt). However, if the author doesn't omit it, could the author then provide a text that was a tad more useful than the firstframe image itself? My answer would be: Yes, but then the author should also update the firstframe image.

2. Objections to the Change Proposal to introduce a new child element to the video element.

We have a Change Proposal to introduce a new child element to the video element.

Keep in mind, you must actually state an objection, not merely cite someone else. If you feel that your objection has already been adequately addressed by someone else, then it is not necessary to repeat it.


Responder Objections to the Change Proposal to introduce a new child element to the video element.
Laura Carlson
Kornel Lesinski * The proposal confuses poster frames with movie posters. It is not purpose of this attribute to serve as a movie poster, and I have not seen any indication of this happening in practice.
* In my experience most videos don't have carefully chosen poster frames that are good description of the video, and many videos have accompanying description which makes description of poster frame unnecessary.
* Description of only a single frame — which sometimes is not even chosen by the video author — can be misleading about video's content.
* I think it's unreasonable to expect that authors would describe both video and poster frame separately, and author's effort is better spent on describing the video itself.
* In case when poster frame is especially interesting, its description could be made part of the video description (it seems unlikely to me that one would like to learn about the poster and not about the video).

The proposal is mainly based on concern that authors *could* use image that contains unique and valuable information about the video. However, this does not happen in practice:

Poster frames on sites like YouTube or Vimeo are just one of the frames of the video. These frames are not specially crafted images that would be a good proxy for the entire video contents. Sometimes these frames capture unimportant scenes from the video, or taken out of context give wrong impression of the video. Such accidental misleading poster frames are a problem for me (sighted user), and I don't think we should be giving *equally bad* experience to users who can't see them.

Some video poster frames, e.g. on InfoQ website, are just website's logo, which tells nothing about the video itself, and website name is obvious from context.

On Guardian and NY Times websites videos seem to have manually chosen poster frames. However, these videos are accompanied by very good descriptions, which are much better than descriptions of poster frames could be (e.g. video about climate change affecting sea life has poster frame with a fisherwoman — even a pefect description of the poster frame would be only an incomplete description of the video).

Videos on movie-oriented websites don't use movie poster for poster frame. Trailers often start with screen describing video rating, and less often logo of a movie studio. This is valuable information, but description of the first frame would only coincidentally contain it (and e.g. if video has rating screen, then users would not get information about movie studio and vice-versa). Instead of relying on poster frame containing *some* information and poster frame description copying it, we should encourage authors to provide information in more reliable and straightforward manner (e.g. Apple trailers website always includes both rating and studio information in movie description, and poster frames are not reliable source of that information).
I strongly object to describing the poster frame separately from the video to AT users. This distinction is not made for sighted users, who have no way of knowing if what they are seeing is the first frame of a video or a poster frame. The poster frame is "intended to be a representative frame of the video" and as such, the description of the video should also be a suitable description of the poster frame. If the poster frames brings attention to any specific aspect of the video, it would be appropriate for the video's description to also stress that aspect. Making the suggested disctinction would encourage inappropriate use of the poster frame.

I strongly object to removing the poster attribute, as it is already implemented by browsers and used by web pages. Adding a short text alternative for the placeholder/poster image (which I object to) does not require changing this part of the syntax.

As a necessary consequence, I also object to renaming the concept from "poster frame" to "first frame", even though I acknowledge that "poster frame" is by no means a perfect name for the feature.

I object to introducing a <firstframe> void element that is likely to appear before the <source> elements. In all browsers that do not implemented support for <firstframe>, any following <source> elements would become child elements of <firstframe> and thus would not be considered in the resource selection algorithm. In effect, that video would be completely broken in those browsers. (Yes, this is also a problem with <track> and introducing new void elements in general.)

The fact that authors can use any image as the poster frame is not sufficient justification. Any frame of the video can also contain arbitrary content, yet there is no mechanism for providing short text alternatives for specific frames on the HTML level. Further, it seems highly unlikely that people who use the poster incorrectly (to include content that is not representative of the video resource itself) would be aware enough to make the effort of making that inappropriate use accessible.

Finally, just like the poster attribute can be used incorrectly, it's possible to use multiple <source> elements with media attributes so that wildly different videos are used depending on the environment. Yet, there is no suggestion to provide a separate text alternatives for each <source>. I object to catering for abuse of the poster attribute but not doing the same for <source> elements.

Comments on Leif Halvard Silli's objections not covered by the above:

There is no disagreement that short text alternatives for the video are important.

There is no contradiction between "conceptually part of the media resource itself" and "should be described as part of the description of the video element itself". The point is quite clear: a short text alternative that is representative of the video would also be suitable as a short text alternative for the poster frame, as the poster frame is representative of the video. No one has suggested that the poster frame be explicitly described in the short text alternative of the video, on the form of "The poster frame contains... and the video itself is about...". That would just as inappropriate as having a separate description for the poster frame.

That <video> does not have a (dedicated) short text alternative is part of the point. Having a dedicated short text alternative for the poster frame but not for the video itself is extremeley backwards. Thus the suggestion that discussion "move on to short and long text alternatives for a media resource as a whole". Note that aria-labelledby and aria-describedby are mentioned as potential solutions in the <firstframe> proposal. This is outside the scope of ISSUE-142, though.
Leif Halvard Silli

More details on responses

  • Laura Carlson: last responded on 12, March 2011 at 13:20 (UTC)
  • Kornel Lesinski: last responded on 12, March 2011 at 19:48 (UTC)
  • : last responded on 13, March 2011 at 09:32 (UTC)
  • Leif Halvard Silli: last responded on 14, March 2011 at 08:40 (UTC)


The following persons have not answered the questionnaire:

  1. Tantek Çelik <tantek@cs.stanford.edu>
  2. Patrick D F Ion <pion@umich.edu>
  3. Judy Brewer <jbrewer@w3.org>
  4. Liam Quin <liam@w3.org>
  5. Richard Ishida <ishida@w3.org>
  6. Chris Wilson <cwilso@google.com>
  7. David Carlisle <davidc@nag.co.uk>
  8. James Helman <jhelman@movielabs.com>
  9. Jim Allan <jimallan@tsbvi.edu>
  10. Chris Marrin <cmarrin@apple.com>
  11. Charles McCathie Nevile <chaals@yandex.ru>
  12. Philippe Le Hégaret <plh@w3.org>
  13. Don Brutzman <brutzman@nps.edu>
  14. T.V. Raman <raman@google.com>
  15. David Singer <singer@apple.com>
  16. Daniel Glazman <daniel.glazman@disruptive-innovations.com>
  17. Karl Dubost <karl@la-grange.net>
  18. Ian Hickson <ian@hixie.ch>
  19. Wu Chou <wu.chou@huawei.com>
  20. Katsuhiko Momoi <momoi@google.com>
  21. Kangchan Lee <chan@w3.org>
  22. Roy Fielding <fielding@gbiv.com>
  23. Deborah Dahl <dahl@conversational-technologies.com>
  24. Michael Cooper <cooper@w3.org>
  25. Glenn Adams <glenn@skynav.com>
  26. Jonathan Jeon <hollobit@etri.re.kr>
  27. David Hyatt <hyatt@apple.com>
  28. WonSuk Lee <wonsuk.lee@etri.re.kr>
  29. Maciej Stachowiak <mjs@apple.com>
  30. Robert Accettura <robert@accettura.com>
  31. Jonathan Watt <jwatt@jwatt.org>
  32. Steve Faulkner <faulkner.steve@gmail.com>
  33. Emmanuelle Gutiérrez y Restrepo <emmanuelle@sidar.org>
  34. Patrick Lauke <redux@splintered.co.uk>
  35. David MacDonald <David100@sympatico.ca>
  36. Jack Jansen <jack@cwi.nl>
  37. Kazuhito Kidachi <k-kidachi@mitsue.co.jp>
  38. Markku Hakkinen <mhakkinen@ets.org>
  39. Jens Oliver Meiert <jens@meiert.com>
  40. Kazuyuki Ashimura <ashimura@w3.org>
  41. Han Xu <collin@w3china.org>
  42. Sam Ruby <rubys@intertwingly.net>
  43. Mark Crawford <mark.crawford@sap.com>
  44. Preety Kumar <preety.kumar@deque.com>
  45. Ian Fette <ifette@google.com>
  46. Cameron McCormack <cam@mcc.id.au>
  47. Stefan Schnabel <stefan.schnabel@sap.com>
  48. Jirka Kosek <jirka@kosek.cz>
  49. Travis Leithead <Travis.Leithead@microsoft.com>
  50. Youngsun Ryu <ysryu@samsung.com>
  51. Sierk Bornemann <sierkb@gmail.com>
  52. James Graham <james@hoppipolla.co.uk>
  53. Henri Sivonen <hsivonen@hsivonen.fi>
  54. Krijn Hoetmer <w3c@qontent.nl>
  55. Channy Yun <channy@gmail.com>
  56. Shane Thacker <shanethacker@gmail.com>
  57. Vilem Malek <murphy@malek.cz>
  58. Zhihong Mao <zhihong.mao@gmail.com>
  59. Benoit Piette <benoit.piette@gmail.com>
  60. Erik van Kempen <erikvankempen@gmail.com>
  61. Dimitri Glazkov <dglazkov@google.com>
  62. Nick Fitzsimons <w3@nickfitz.co.uk>
  63. Josh Lawton <w3c@joshlawton.com>
  64. S Emerson <w3c@accretewebsolutions.ca>
  65. Theresa O'Connor <eoconnor@apple.com>
  66. Justin Anthony Knapp <justinkoavf@gmail.com>
  67. Simon Myers <Smylers@stripey.com>
  68. Samuel Weinig <weinig@apple.com>
  69. Alexey Proskuryakov <ap@webkit.org>
  70. Alejandro Fernandez <alejandro@mediadvanced.com>
  71. Doug Jones <doug_b_jones@me.com>
  72. Marc Drumm <mdrumm@wcupa.edu>
  73. Danny Liang <danny.glue@gmail.com>
  74. Michael Puls II <shadow2531@gmail.com>
  75. Ron Reisor <ron@udel.edu>
  76. Craig Buckler <craigbuckler@gmail.com>
  77. Dale Hudjik <dale.hudjik@gmail.com>
  78. James Cassell <w3c@cyberpear.com>
  79. Joseph D'Andrea <jdandrea@gmail.com>
  80. Eric Carlson <eric.carlson@apple.com>
  81. Don Kiely <donkiely@computer.org>
  82. David Child <dave@addedbytes.com>
  83. Mark DuBois <Mark@webprofessionals.org>
  84. David Bills <w3@dfbills.com>
  85. Nik Thierry <me@thisemail.ca>
  86. Andrew Ramsden <andrew@irama.org>
  87. John Foliot <john.foliot@deque.com>
  88. Shefik Macauley <allknightaccess@gmail.com>
  89. Joe Steele <steele@adobe.com>
  90. John Vernaleo <john@netpurgatory.com>
  91. Jeremy Keith <jeremy@adactio.com>
  92. Jedi Lin <JediLin@Gmail.com>
  93. Jon Hughes <jon@phazm.com>
  94. Samuel Santos <samaxes@gmail.com>
  95. Dean Jackson <dino@apple.com>
  96. Mohammed DADAS <mohammed.dadas@orange.com>
  97. Sally Cain <sally.cain@rnib.org.uk>
  98. David Bolter <dbolter@mozilla.com>
  99. James Craig <jcraig@apple.com>
  100. Leonard Rosenthol <lrosenth@adobe.com>
  101. Jean-Pierre EVAIN <evain@ebu.ch>
  102. Mark Pilgrim <pilgrim@google.com>
  103. Matt Lee <mattl@cnuk.org>
  104. Magnus Olsson <magnus.olsson@ericsson.com>
  105. Chris Pearce <cpearce@mozilla.com>
  106. Andrew Wilson <atwilson@google.com>
  107. Per-Erik Brodin <per-erik.brodin@ericsson.com>
  108. Ojan Vafai <ojan@chromium.org>
  109. Martin McEvoy <martin@weborganics.co.uk>
  110. Aryeh Gregor <ayg@aryeh.name>
  111. Anders Bondehagen <anders@bondehagen.com>
  112. Steven Pemberton <Steven.Pemberton@cwi.nl>
  113. Raul Hudea <rhudea@adobe.com>
  114. Raghavan Gurumurthy <raghavan@adobe.com>
  115. Mayank Kumar <mayankk@adobe.com>
  116. Dragos Georgita <dgeorgit@adobe.com>
  117. Christopher Bank <cbank@adobe.com>
  118. Ole Riesenberg <or@oleriesenberg.com>
  119. Takuya Oikawa <takuya@google.com>
  120. Jatinder Mann <jmann@microsoft.com>
  121. Robert Stern <rstern@gmail.com>
  122. Eihab Ibrahim <eihabibrahim@gmail.com>
  123. Kensaku KOMATSU <kensaku.komatsu@gmail.com>
  124. Jer Noble <jer.noble@apple.com>
  125. Masatomo Kobayashi <mstm@jp.ibm.com>
  126. Peter Beverloo <beverloo@google.com>
  127. Andrew Scherkus <scherkus@google.com>
  128. Greg Johnson <greg.johnson@gmail.com>
  129. Martijn Croonen <martijn@martijnc.be>
  130. Stanley Manoski <manoski@mitre.org>
  131. Mounir Lamouri <mlamouri@google.com>
  132. Tony Gentilcore <tonyg@google.com>
  133. Joseph Pecoraro <pecoraro@apple.com>
  134. Bob Lund <b.lund@cablelabs.com>
  135. Tatsuya Igarashi <Tatsuya.Igarashi@sony.com>
  136. John Simmons <johnsim@microsoft.com>
  137. Mark Watson <watsonm@netflix.com>
  138. Clarke Stevens <c.stevens@cablelabs.com>
  139. Mark Vickers <mark_vickers@comcast.com>
  140. Jeremy LaCivita <jeremy.lacivita@comcast.com>
  141. Denis Ah-Kang <denis@w3.org>
  142. Alvar Laigna <laigna@gmail.com>
  143. Kunio Ito <kunio.ito@mail.rakuten.com>
  144. David Mays <david_mays@comcast.com>
  145. Michael Chen <michael_chen@comcast.com>
  146. jongyoul Park <jongyoul@etri.re.kr>
  147. Reinaldo Ferraz <reinaldo@nic.br>
  148. Eva Lingyun Jing <jinglingyun@baidu.com>
  149. GANG LIANG <gang.liang@huawei.com>
  150. Ryosuke Niwa <rniwa@apple.com>
  151. Gian Luca Marroni <gmarroni@libero.it>
  152. Ian Devlin <ian@iandevlin.com>
  153. Xingrong Guo <guoxingrong@baidu.com>
  154. Jet Villegas <w3c@junglecode.net>
  155. Alexander Surkov <surkov.alexander@gmail.com>
  156. Hasan Savran <hsavran@kent.edu>
  157. Eric VonColln <eric.voncolln@navy.mil>
  158. Jungkee Song <jungkee.song@samsung.com>
  159. Rayi Lei <leiyi@baidu.com>
  160. David Dorwin <ddorwin@google.com>
  161. jiexuan gao <gaojiexuan@baidu.com>
  162. Xiaoqing Yang <yangxiaoqing@baidu.com>
  163. Aaron Colwell <acolwell@google.com>
  164. Alex Giladi <alex.giladi@huawei.com>
  165. Motomasa Futagami <Motomasa.Futagami@jp.sony.com>
  166. Kevin Streeter <kstreete@adobe.com>
  167. Christian Kaiser <kaiserc@google.com>
  168. Xuejian Li <lixuejian@baidu.com>
  169. Zuncheng Yang <yangzuncheng@baidu.com>
  170. Qianglong Zheng <zhengqianglong@baidu.com>
  171. Zhou Shen <shenzhou@baidu.com>
  172. Duoyi Wu <wuduoyi@baidu.com>
  173. Zheng Jia <jiazheng@baidu.com>
  174. Weifeng Feng <fengweifeng@baidu.com>
  175. Damin Hu <hudamin@baidu.com>
  176. Yang Liu <liuyang12@baidu.com>
  177. Zhixing Lei <leizhixing@baidu.com>
  178. Honggang Tang <tanghonggang@baidu.com>
  179. Kefeng Li <buaadallas@gmail.com>
  180. Xu Ma <maxu@baidu.com>
  181. Junzhong Liu <liujunzhong@baidu.com>
  182. Stefan Kaiser <stefan.kaiser@fokus.fraunhofer.de>
  183. Stefan Pham <stefan.pham@fokus.fraunhofer.de>
  184. Ami Fischman <fischman@google.com>
  185. Arnaud Braud <arnaud.braud@orange.com>
  186. Futomi Hatano <futomi.hatano@newphoria.co.jp>
  187. Bram Tullemans <tullemans@ebu.ch>
  188. Petr Peterka <ppeterka@verimatrix.com>
  189. lei wang <wanglei03@baidu.com>
  190. Milan Patel <Milan.Patel@huawei.com>
  191. Yiling Gu <guyiling@baidu.com>
  192. Zefa Xiong <xiongzefa@baidu.com>
  193. shanglin chen <chenshanglin@baidu.com>
  194. Ping Wu <wuping02@baidu.com>
  195. Bin Chen <chenbin01@baidu.com>
  196. Youichi Takashima <takashima.youichi@lab.ntt.co.jp>
  197. Patrick Ladd <Pat_Ladd2@comcast.com>
  198. Norifumi Kikkawa <norifumi.kikkawa@jp.sony.com>
  199. Hao Jing <jh.jinghao@huawei.com>
  200. Glenn Deen <glenn.deen@nbcuni.com>
  201. Lei Wang <wanglei@baidu.com>
  202. Tom Handal <thandal@verimatrix.com>
  203. Pengcheng Guo <guopengcheng@baidu.com>
  204. Tom Wiltzius <wiltzius@google.com>
  205. Pierre-Anthony Lemieux <pal@sandflow.com>
  206. Xie Jianhui <xiejianhui@baidu.com>
  207. Yujie Jiang <jiangyujie@baidu.com>
  208. Kazuhiko Takabayashi <kazuhiko.takabayashi@jp.sony.com>
  209. Brady Eidson <beidson@apple.com>
  210. Michael Thornburgh <mthornbu@adobe.com>
  211. Mick Hakobyan <mhakobyan@netflix.com>
  212. Vladimir Sinelnikov <sinelnikov@gmail.com>
  213. Chris Wong <huanghoujin@baidu.com>
  214. Yiliang LIU <liuyiliang@baidu.com>
  215. mingqiang zhang <imcnan@gmail.com>
  216. Suzanne Taylor <Suzanne.Taylor@pearson.com>
  217. Grzegorz Babula <gbabula@gmail.com>
  218. Brian Kardell <hitchjs@gmail.com>
  219. xueliang fan <fanxueliang@baidu.com>
  220. Niels Thorwirth <nthorwirth@verimatrix.com>
  221. David Evans <david.evans@rd.bbc.co.uk>
  222. Joseph Karr O'Connor <josephoconnor@mac.com>
  223. Yusuke Kagiwada <block.rxckin.beats@gmail.com>
  224. smallni ding <smallniding@tencent.com>
  225. Jim Walsh <jim@jwalshcreative.com>
  226. Greg Davis <greg.davis@pearson.com>
  227. Gabino Alonso <gabinovincent@gmail.com>
  228. Sam Langdon <sam.langdon@hachette.co.uk>
  229. Michael Kelly <mkelly@mozilla.com>
  230. Xiaoqian Wu <xiaoqian@w3.org>
  231. Yue Min <minyue@baidu.com>
  232. Min Li <limin04@baidu.com>
  233. Joanmarie Diggs <jdiggs@igalia.com>
  234. Pedro Xavier Jorge <pedro.xavierjorge@gmail.com>
  235. Akira Torii <Torii.Akira@bp.MitsubishiElectric.co.jp>
  236. So Vang <svang@nab.org>
  237. Nathalia Sautchuk Patrício <nathalia@nic.br>
  238. Vicente García Díaz <vicegd@live.com>
  239. Shinya Maruyama <Shinya.Maruyama@jp.sony.com>
  240. Yusuke Yokosuka <Yokosuka.Yusuke@bx.MitsubishiElectric.co.jp>
  241. John Riviello <john_riviello@comcast.com>
  242. yaolong wang <wangyaolong@baidu.com>
  243. Tao Liang <liangtao01@baidu.com>
  244. Glenn Eguchi <geguchi@adobe.com>
  245. Lukáš Čihák <lukas.cihak@mensa.cz>
  246. WOOGLAE KIM <wlkim@inswave.com>
  247. Min Ren <minren@tencent.com>
  248. Jason White <jjwhite@ets.org>
  249. Hyejin Lee <hjlee@html5forum.or.kr>
  250. Richard Grzeczkowski <richard_grzeczkowski@comcast.com>
  251. Pascal Perrot <pascal.perrot@orange.com>
  252. Dapeng Liu <max.ldp@alibaba-inc.com>
  253. Matthew Wolenetz <wolenetz@google.com>
  254. Cory Heslip <cory_heslip@comcast.com>
  255. Shaohang Yang <shaohang.ysh@alibaba-inc.com>
  256. Seiji Okumura <Okumura.Seiji@bc.MitsubishiElectric.co.jp>
  257. Eiji Yamamoto <Yamamoto.Eiji@db.MitsubishiElectric.co.jp>
  258. Ali C. Begen <ali_begen@comcast.com>
  259. HENGBING LIU <herbertliu@tencent.com>

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 (preferred) or by mail to sysreq.