W3C WBS Home

Results of Questionnaire ISSUE-74: canvas-accessibility and ISSUE-105 canvas-usemap - Straw Poll for Objections

The results of this questionnaire are available to anybody.

This questionnaire was open from 2010-10-13 to 2010-10-21.

8 answers have been received.

Jump to results for question:

  1. Objections to adding a boolean nonav attribute to the canvas to hide its contents from AT and keyboard navigation
  2. Objections to removing the ability to use the children of canvas as an accessible dom entirely, in favor of other techniques, such as usemap?
  3. Objections to adding advisory text explaining how to use the focus rect API for efficient caret position notification, and change nothing else?
  4. Objections to adding image map / usemap support as a possible way to represent focusable regions on the canvas?

1. Objections to adding a boolean nonav attribute to the canvas to hide its contents from AT and keyboard navigation

This option is:

If you have strong objections to adopting this option, 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.

Details

Responder Objections to adding a boolean nonav attribute to the canvas to hide its contents from AT and keyboard navigation
Richard Schwerdtfeger I have no issue with removing -nonav as long as the text regarding the canvas subtree states that there is a 1 for 1 navigational mapping to UI elements drawn on the physical canvas as it states today. In short whatever is in the subtree must be a a representation of what you see on the physical canvas at all times. This is much different from having a fallback that is an alternative for the canvas used as say a long description. This would not constitute a one for one mapping.
Ian Hickson This is already supported by the simple means of removing the contents of a <canvas> element using script. This handles all the use cases that might apply. (Bear in mind that we know script is enabled if the fallback is unnecessary, since otherwise the <canvas> wouldn't work in the first place.)
Cynthia Shelly I see nonav as a "nice to have" feature. I have no objection to removing or keeping it.
Steve Faulkner
Martin Kliehm
Eric Eggert
Frank Olivier the attribute seems superfluous; canvas authors can correctly handle fallback and a11y considerations with the method that Ian describes.
Eric Carlson

2. Objections to removing the ability to use the children of canvas as an accessible dom entirely, in favor of other techniques, such as usemap?

This option is:

If you have strong objections to adopting this option, 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.

Details

Responder Objections
Richard Schwerdtfeger This proposal is currently irrelevant. The canvas subtree as the spec. currently reads allows for an accessible DOM subtree by default. No special -adom attribute is required -now.

Here is the text from the HTML 5 spec regarding the <canvas> element:

"When a canvas element represents embedded content, the user can still focus descendants of the canvas element (in the fallback content). This allows authors to make an interactive canvas keyboard-focusable: authors should have a one-to-one mapping of interactive regions to focusable elements in the fallback content."

Ian Hickson Image maps have not been demonstrated to be usable to create accessible image maps.
Cynthia Shelly The accessible DOM sub-tree is implemented in IE9, and is currently in the HTML 5 spec. usemap is "nice to have" in addtion to the accessible DOM sub-tree, but does not cover all of the use cases, and is not a replacement. This issue seems to be overcome by events.
Steve Faulkner I object to removing the ability to use the children of canvas as an accessible DOM, this feature is an important aspect of making canvas conetnt accessible. This should be provided in comjunction with other techniques.
Martin Kliehm
Eric Eggert
Frank Olivier This is the best current solution to solving canvas a11y; it is a familiar solution for authors - build an interface using HTML elements.
Eric Carlson

3. Objections to adding advisory text explaining how to use the focus rect API for efficient caret position notification, and change nothing else?

This option is:

If you have strong objections to adopting this option, 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.

Details

Responder Objections to adding advisory text explaining how to use the focus rect API for efficient caret position notification, and change nothing else?
Richard Schwerdtfeger This is inadequate. I completely object to this proposal. What is in the specification is inadequate if people do something like rich text editing.

The poll does not include our proposal for adding an API to support caret and selection. This proposal should have been included in the survey.
Ian Hickson
Cynthia Shelly This approach does not solve the problem for more complex applications. While the editor may feel that it is a mis-use of canvas to create a text editor in canvas, it is technically feasible, and and seems a likely scenario given the desire of web applicaiton developers to have greater control over the presenation of their applciations. Unless there is a way to prevent this use of canvas (and I don't think there is) then we need to provide a way for it be made accessible to a variety of assitive technologies.

I think there may be an error in the survey, as question #1 was supposed to be an item relating to "Change proposal to provide accessiblity info for driving screen magnifier tracking..." which I support. It appears instead that items 2&3 are duplicates.
Steve Faulkner I object to ONLY adding advisory information without adding features, the focus ring on its own is an inadequate tool for providing accessibility information to ATs. More information is required to be exposed to ATs in order for canvas accessibility features to be flexible enough for current and future usage scenarios. If not provided in the browser, developers who wish to provide accessible canvas content will be forced to hack around the lack of accessibility support, as experience with developer based accessibility hacks tells us, this is not a desirable or generally psotive outcome and will do a disservice to users with disabilities.
Martin Kliehm
Eric Eggert
Frank Olivier I've been looking into what one would need to do to have a full-featured text input / canvas text drawing solution - and there is a very significant amount of work that a UA/author would have to do to make this work without any loss in functionality (compared to the native text entry elements).
Eric Carlson Implementing a text editor in canvas is clearly ill advised, and the spec *should* contain cautionary text. The text proposed by Ian will make an excellent addition to the spec, although it should not be the only change for canvas accessibility.

4. Objections to adding image map / usemap support as a possible way to represent focusable regions on the canvas?

This option is:

If you have strong objections to adopting this option, 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.

Details

Responder Objections to adding image map / usemap support as a possible way to represent focusable regions on the canvas?
Richard Schwerdtfeger I would support providing this as a way to make canvas accessible but it should not be the only vehicle. I would categorize this as a nice to have feature. Also, someone needs to drive this forward as it would require, in many cases, having a full DOM subtree with support for pop-up menus, etc.

This approach has some benefits as well as limitations over the DOM subtree. A a nice to have is allowing the map to automatically draw the focus ring without a specific drawing call to achieve it. This would not work for things like selected items in menus or listboxes. So, this would also require a caret/selection API to drive magnification.
Ian Hickson Image maps have not been demonstrated to be usable to create accessible image maps. We should not add features that are hard to use, especially when they are only useful for limited (simple) cases.
Cynthia Shelly This is a "nice to have" feature, in addition to an accessible DOM sub-tree. I have no objection to its inclusion, but think it is a lower priority work item than an accessible DOM sub-tree with magnification and caret support.
Steve Faulkner There has been no technical arguments against the addition of an image map feature to canvas. There has been a willingness shown by implementors to add the feature. There has been examples (http://www.paciellogroup.com/blog/misc/canvas-pie/pie.html) of how it would work provided (via hacking a transparent image map over the top of a canvas). There has been no indication that the addition of this feature will cause an undue development burden on implementors. There has been no change proposal objecting to this addition. While not a complete solution it could prove to be a worthwhile method in cases where complex interaction is not required, but clickable/focusable canvas areas are. The major adavantages of this method are that it is familiar to authors, many html editors have image map editors built in, the creation of a clickable area using image map also provides a programmatically determinable focus ring and it responds to keyboard input by default.
Martin Kliehm
Eric Eggert
Frank Olivier no objection, but it is a lower priority work item
Eric Carlson

More details on responses

Non-responders

The following persons have not answered the questionnaire:

  1. Tantek Çelik <tantek@cs.stanford.edu>
  2. Patrick D F Ion <ion@ams.org>
  3. Judy Brewer <jbrewer@w3.org>
  4. Wayne Carr <wayne.carr@linux.intel.com>
  5. Jason White <jason@jasonjgw.net>
  6. Liam Quin <liam@w3.org>
  7. Richard Ishida <ishida@w3.org>
  8. Chris Wilson <cwilso@google.com>
  9. Wendy Chisholm <wendc@microsoft.com>
  10. David Carlisle <davidc@nag.co.uk>
  11. James Helman <jhelman@movielabs.com>
  12. Jim Allan <jimallan@tsbvi.edu>
  13. Chris Marrin <cmarrin@apple.com>
  14. Charles McCathie Nevile <chaals@yandex-team.ru>
  15. Philippe Le Hégaret <plh@w3.org>
  16. Arthur Barstow <art.barstow@gmail.com>
  17. T.V. Raman <raman@google.com>
  18. David Singer <singer@apple.com>
  19. Daniel Glazman <daniel.glazman@disruptive-innovations.com>
  20. Sean Hayes <sean.hayes@microsoft.com>
  21. Karl Dubost <karl@la-grange.net>
  22. Larry Masinter <masinter@adobe.com>
  23. David Baron <dbaron@dbaron.org>
  24. Lisa Seeman <lisa.seeman@zoho.com>
  25. Paul Cotton <Paul.Cotton@microsoft.com>
  26. Shane McCarron <shane@aptest.com>
  27. wu chou <wu.chou@huawei.com>
  28. Katsuhiko Momoi <momoi@google.com>
  29. Kangchan Lee <chan@w3.org>
  30. Roy Fielding <fielding@gbiv.com>
  31. Silvia Pfeiffer <silviapfeiffer1@gmail.com>
  32. Johnny Stenback <jst@mozilla.com>
  33. Janina Sajka <janina@rednote.net>
  34. Deborah Dahl <dahl@conversational-technologies.com>
  35. Frederick Hirsch <w3c@fjhirsch.com>
  36. Michael Cooper <cooper@w3.org>
  37. Glenn Adams <glenn@skynav.com>
  38. Jonathan Jeon <hollobit@etri.re.kr>
  39. David Hyatt <hyatt@apple.com>
  40. Robin Berjon <robin@w3.org>
  41. WonSuk Lee <wonsuk11.lee@samsung.com>
  42. Maciej Stachowiak <mjs@apple.com>
  43. Robert Accettura <robert@accettura.com>
  44. Jonathan Watt <jwatt@jwatt.org>
  45. Emmanuelle Gutiérrez y Restrepo <emmanuelle@sidar.org>
  46. Patrick Lauke <redux@splintered.co.uk>
  47. David MacDonald <David100@sympatico.ca>
  48. Jack Jansen <jack@cwi.nl>
  49. Boris Zbarsky <bzbarsky@mit.edu>
  50. Kazuhito Kidachi <k-kidachi@mitsue.co.jp>
  51. Markku Hakkinen <mhakkinen@ets.org>
  52. Cyril Concolato <cyril.concolato@telecom-paristech.fr>
  53. Gez Lemon <glemon@paciellogroup.com>
  54. Pasquale Popolizio <p.popolizio@webprofession.com>
  55. Luca Mascaro <l.mascaro@webprofession.com>
  56. Markus Mielke <mmielke@microsoft.com>
  57. Arun Ranganathan <arun@mozilla.com>
  58. Jens Meiert <jens@meiert.com>
  59. Felix Sasaki <fsasaki@w3.org>
  60. Kazuyuki Ashimura <ashimura@w3.org>
  61. Daniel Burnett <dburnett@voxeo.com>
  62. Tomas Caspers <tomas@tomascaspers.de>
  63. Han Xu <collin@w3china.org>
  64. Sam Ruby <rubys@intertwingly.net>
  65. Jonas Sicking <jonas@sicking.cc>
  66. Mark Crawford <mark.crawford@sap.com>
  67. Doug Schepers <schepers@w3.org>
  68. Ian Fette <ifette@google.com>
  69. Michael[tm] Smith <mike@w3.org>
  70. Julian Reschke <julian.reschke@gmx.de>
  71. Kelly Ford <kelly.ford@microsoft.com>
  72. Cameron McCormack <cam@mcc.id.au>
  73. Jirka Kosek <jirka@kosek.cz>
  74. Robert O'Callahan <robert@ocallahan.org>
  75. Travis Leithead <Travis.Leithead@microsoft.com>
  76. Youngsun Ryu <ysryu@samsung.com>
  77. Sierk Bornemann <sierkb@gmail.com>
  78. Martijn Wargers <martijn.martijn@gmail.com>
  79. Simon Pieters <simonp@opera.com>
  80. James Graham <james@hoppipolla.co.uk>
  81. Henri Sivonen <hsivonen@hsivonen.fi>
  82. Lachlan Hunt <lachlan.hunt@lachy.id.au>
  83. Krijn Hoetmer <w3c@qontent.nl>
  84. Markus Fischer <markus@fischer.name>
  85. Dean Edridge <dean@dean.kiwi>
  86. Channy Yun <channy@gmail.com>
  87. Shane Thacker <shanethacker@gmail.com>
  88. Bill Mason <billm@accessibleinter.net>
  89. Vilem Malek <murphy@malek.cz>
  90. Zhihong Mao <zhihong.mao@gmail.com>
  91. Benoit Piette <benoit.piette@gmail.com>
  92. Erik van Kempen <erikvankempen@gmail.com>
  93. Jude Robinson <dotcode+w3@gmail.com>
  94. Dimitri Glazkov <dglazkov@google.com>
  95. Diego La Monica <d.lamonica@webprofession.com>
  96. Nick Fitzsimons <w3@nickfitz.co.uk>
  97. Josh Lawton <w3c@joshlawton.com>
  98. Giovanni Gentili <giovanni.gentili@gmail.com>
  99. Adele Peterson <adele@apple.com>
  100. S Emerson <w3c@accretewebsolutions.ca>
  101. Morten Tollefsen <morten@medialt.no>
  102. Daniel Schattenkirchner <schattenkirchner.daniel@gmx.de>
  103. Edward O'Connor <eoconnor@apple.com>
  104. Justin Anthony Knapp <justinkoavf@gmail.com>
  105. Simon Myers <Smylers@stripey.com>
  106. Samuel Weinig <weinig@apple.com>
  107. Alexey Proskuryakov <ap@webkit.org>
  108. Alejandro Fernandez <alejandro@mediadvanced.com>
  109. Doug Jones <doug_b_jones@me.com>
  110. Marc Drumm <mdrumm@wcupa.edu>
  111. Danny Liang <danny.glue@gmail.com>
  112. Arne Johannessen <arne@thaw.de>
  113. Michael Puls II <shadow2531@gmail.com>
  114. Ron Reisor <ron@udel.edu>
  115. Marat Tanalin <mtanalin@yandex.ru>
  116. Andrew Norman <idonothaveacat@gmail.com>
  117. Craig Buckler <craigbuckler@gmail.com>
  118. Matthew Turvey <mcturvey@gmail.com>
  119. Dale Hudjik <dale.hudjik@gmail.com>
  120. James Cassell <w3c@cyberpear.com>
  121. Joseph D'Andrea <jdandrea@gmail.com>
  122. Pietro Russo <p.russo@webprofession.com>
  123. Moto Ishizawa <summerwind.jp+w3c@gmail.com>
  124. Chris Adams <chris@tuesdaybegins.com>
  125. Michael Turnwall <w3c@turnwall.net>
  126. Don Kiely <donkiely@computer.org>
  127. Robert Marshall <rdm@rdmsoft.com>
  128. Jane Lee <applegoddess@gmail.com>
  129. David Child <dave@addedbytes.com>
  130. Mark DuBois <Mark@webprofessionals.org>
  131. David Choi <daaave@gmail.com>
  132. Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
  133. David Bills <w3@dfbills.com>
  134. Nik Thierry <me@thisemail.ca>
  135. Andrew Ramsden <andrew@irama.org>
  136. John Foliot <john@foliot.ca>
  137. Shefik Macauley <allknightaccess@gmail.com>
  138. Joe Steele <steele@adobe.com>
  139. John Vernaleo <john@netpurgatory.com>
  140. Jeremy Keith <jeremy@adactio.com>
  141. Jedi Lin <JediLin@Gmail.com>
  142. Manu Sporny <msporny@digitalbazaar.com>
  143. Kenny Johar <kensingh@microsoft.com>
  144. Jon Hughes <jon@phazm.com>
  145. Anssi Kostiainen <anssi.kostiainen@intel.com>
  146. Samuel Santos <samaxes@gmail.com>
  147. Dean Jackson <dino@apple.com>
  148. Mohammed DADAS <mohammed.dadas@orange.com>
  149. Sally Cain <sally.cain@rnib.org.uk>
  150. Dan Romascanu <dromasca@avaya.com>
  151. David Bolter <dbolter@mozilla.com>
  152. Chris Double <cdouble@mozilla.com>
  153. Jeanne F Spellman <jeanne@w3.org>
  154. James Craig <jcraig@apple.com>
  155. MING JIN <ming.jin.web@gmail.com>
  156. Leonard Rosenthol <lrosenth@adobe.com>
  157. Philip Jägenstedt <philipj@opera.com>
  158. Adrian Bateman <adrianba@microsoft.com>
  159. Dionysios Synodinos <synodinos@gmail.com>
  160. Jean-Pierre EVAIN <evain@ebu.ch>
  161. Mark Pilgrim <pilgrim@google.com>
  162. Matt Lee <mattl@cnuk.org>
  163. Magnus Olsson <magnus.olsson@ericsson.com>
  164. Carlos Cecconi <cecconi@nic.br>
  165. Chris Pearce <cpearce@mozilla.com>
  166. Dzung Tran <dzung.d.tran@intel.com>
  167. Mark Miller <erights@google.com>
  168. Andrew Wilson <atwilson@google.com>
  169. Per-Erik Brodin <per-erik.brodin@ericsson.com>
  170. Ojan Vafai <ojan@chromium.org>
  171. Martin McEvoy <martin@weborganics.co.uk>
  172. Aryeh Gregor <ayg@aryeh.name>
  173. Gavin Carothers <gavin@carothers.name>
  174. Eliot Graff <eliotgra@microsoft.com>
  175. Jonathan Griffin <jgriffin@mozilla.com>
  176. Kris Krueger <krisk@microsoft.com>
  177. Erik Isaksen <erik_isaksen@hotmail.com>
  178. Anders Bondehagen <anders@bondehagen.com>
  179. Steven Pemberton <Steven.Pemberton@cwi.nl>
  180. Raul Hudea <rhudea@adobe.com>
  181. Raghavan Gurumurthy <raghavan@adobe.com>
  182. Mayank Kumar <mayankk@adobe.com>
  183. Monikandan S <smonikan@adobe.com>
  184. Dragos Georgita <dgeorgit@adobe.com>
  185. Christopher Bank <cbank@adobe.com>
  186. Dominik Tomaszuk <ddooss@wp.pl>
  187. Ole Riesenberg <or@oleriesenberg.com>
  188. Takuya Oikawa <takuya@google.com>
  189. Jatinder Mann <jmann@microsoft.com>
  190. Robert Stern <rstern@gmail.com>
  191. Dean Leigh <dean.leigh@deanleigh.co.uk>
  192. Eihab Ibrahim <eihabibrahim@gmail.com>
  193. Kensaku KOMATSU <kensaku.komatsu@gmail.com>
  194. Ian Pouncey <w3c@ipouncey.co.uk>
  195. Jer Noble <jer.noble@apple.com>
  196. Léonie Watson <lwatson@paciellogroup.com>
  197. Masatomo Kobayashi <mstm@jp.ibm.com>
  198. Grant Simpson <glsimpso@gmail.com>
  199. Peter Beverloo <beverloo@google.com>
  200. Andrew Scherkus <scherkus@google.com>
  201. Greg Johnson <greg.johnson@gmail.com>
  202. Martijn Croonen <martijn@martijnc.be>
  203. John Jansen <johnjan@microsoft.com>
  204. Stanley Manoski <manoski@mitre.org>
  205. Jonas Schneider <js.sokrates@gmail.com>
  206. Yosuke Funahashi <yosuke@funahashi.cc>
  207. Mounir Lamouri <mlamouri@google.com>
  208. Mike Amundsen <mamund@yahoo.com>
  209. Tony Gentilcore <tonyg@google.com>
  210. Jacob Rossi <Jacob.Rossi@microsoft.com>
  211. Joseph Pecoraro <pecoraro@apple.com>
  212. Othmane Benyoucef <othmane_benyoucef@hotmail.com>
  213. Shoko Okuma <okuma@tomo-digi.co.jp>
  214. Fumitaka Watanabe <fwtnb@tomo-digi.co.jp>
  215. Yoshimitsu Tsurimaki <tsurimaki@tomo-digi.co.jp>
  216. Juhani Huttunen <juhani.huttunen@nokia.com>
  217. Bob Lund <b.lund@cablelabs.com>
  218. Tatsuya Igarashi <Tatsuya.Igarashi@jp.sony.com>
  219. John Simmons <johnsim@microsoft.com>
  220. Mathias Bynens <mathias@qiwi.be>
  221. Mark Watson <watsonm@netflix.com>
  222. Clarke Stevens <c.stevens@cablelabs.com>
  223. Mark Vickers <mark_vickers@cable.comcast.com>
  224. Sree Kotay <Sree_Kotay@cable.comcast.com>
  225. Cameron Jones <cmhjones@gmail.com>
  226. Rik Cabanier <Cabanier@adobe.com>
  227. Denis Ah-Kang <denis@w3.org>
  228. Alvar Laigna <laigna@gmail.com>
  229. Kunio Ito <kunio.ito@mail.rakuten.com>
  230. David Mays <david_mays@comcast.com>
  231. Michael Chen <michael_chen@cable.comcast.com>
  232. jongyoul Park <jongyoul@etri.re.kr>
  233. Adrian Roselli <roselli@algonquinstudios.com>
  234. Colin Ihrig <cjihrig@gmail.com>
  235. Kilroy Hughes <kilroy.hughes@microsoft.com>
  236. Reinaldo Ferraz <reinaldo@nic.br>
  237. Bill Mandel <bill.mandel@nbcuni.com>
  238. Jonas Jacek <w3c@jonas.me>
  239. Eva Lingyun Jing <jinglingyun@baidu.com>
  240. GANG LIANG <gang.liang@huawei.com>
  241. Ryosuke Niwa <rniwa@apple.com>
  242. Jason Kiss <jason@accessibleculture.org>
  243. Gian Luca Marroni <gmarroni@libero.it>
  244. Ian Devlin <ian@iandevlin.com>
  245. Greg Billock <gbillock@google.com>
  246. Xingrong Guo <guoxingrong@baidu.com>
  247. Jet Villegas <w3c@junglecode.net>
  248. Anas R. <anas.ram@gmail.com>
  249. Alexander Surkov <surkov.alexander@gmail.com>
  250. wilfred nas <wilfred@wnas.nl>
  251. Hasan Savran <hsavran@kent.edu>
  252. Ben Dalton <bendalton@gmail.com>
  253. Marco Kotrotsos <Marco@mlabs.nl>
  254. Brian Blakely <anewpage.media@gmail.com>
  255. Eric VonColln <eric.voncolln@navy.mil>
  256. Jason Boyd <jason@pixelboxdesign.co.uk>
  257. Jerry Jiang <jerry@ucweb.com>
  258. Arun Patole <arun.patole@motorola.com>
  259. Jungkee Song <jungkee.song@samsung.com>
  260. Huan Ren <renhuan@360.cn>
  261. Xitong Huang <stonehuang@tencent.com>
  262. Songnan Ran <ransn@ucweb.com>
  263. Rayi Lei <leiyi@baidu.com>
  264. Daniel Austin <daniel.austin@grintech.net>
  265. David Dorwin <ddorwin@google.com>
  266. jiexuan gao <gaojiexuan@baidu.com>
  267. Mathew Marquis <mat@matmarquis.com>
  268. Xiaoqing Yang <yangxiaoqing@baidu.com>
  269. Aaron Colwell <acolwell@google.com>
  270. Alex Giladi <alex.giladi@huawei.com>
  271. Motomasa Futagami <Motomasa.Futagami@jp.sony.com>
  272. Kevin Streeter <kstreete@adobe.com>
  273. jean-baptiste henry <j.henry.ext@viaccess.com>
  274. Christian Kaiser <kaiserc@google.com>
  275. François REMY <francois.remy.dev@outlook.com>
  276. Xuejian Li <lixuejian@baidu.com>
  277. Zuncheng Yang <yangzuncheng@baidu.com>
  278. Qianglong Zheng <zhengqianglong@baidu.com>
  279. Zhou Shen <shenzhou@baidu.com>
  280. Duoyi Wu <wuduoyi@baidu.com>
  281. Zheng Jia <jiazheng@baidu.com>
  282. Weifeng Feng <fengweifeng@baidu.com>
  283. Damin Hu <hudamin@baidu.com>
  284. Yang Liu <liuyang12@baidu.com>
  285. Zhixing Lei <leizhixing@baidu.com>
  286. Honggang Tang <tanghonggang@baidu.com>
  287. Kefeng Li <buaadallas@gmail.com>
  288. Manyoung Cho <manyoung@w3labs.kr>
  289. Xu Ma <maxu@baidu.com>
  290. Junzhong Liu <liujunzhong@baidu.com>
  291. Yusuke Maehama <maehama@tomo-digi.co.jp>
  292. Stefan Kaiser <stefan.kaiser@fokus.fraunhofer.de>
  293. Sheau Ng <Sheau.ng@nbcuni.com>
  294. Stefan Pham <stefan.pham@fokus.fraunhofer.de>
  295. Ami Fischman <fischman@google.com>
  296. Arnaud Braud <arnaud.braud@orange.com>
  297. Futomi Hatano <futomi.hatano@newphoria.co.jp>
  298. Bram Tullemans <tullemans@ebu.ch>
  299. Petr Peterka <ppeterka@verimatrix.com>
  300. lei wang <wanglei03@baidu.com>
  301. Milan Patel <Milan.Patel@huawei.com>
  302. Yiling Gu <guyiling@baidu.com>
  303. Yehuda Katz <wycats@gmail.com>
  304. Jay Munro <jay@techtoons.com>
  305. Xueqing Huang <huangxueqing@baidu.com>
  306. Zefa Xiong <xiongzefa@baidu.com>
  307. shanglin chen <chenshanglin@baidu.com>
  308. Yaso Córdova <yaso@nic.br>
  309. Dongsheng Zhang <zhangdongsheng@baidu.com>
  310. Ping Wu <wuping02@baidu.com>
  311. Yao Tong <tongyao@baidu.com>
  312. Bin Chen <chenbin01@baidu.com>
  313. Youichi Takashima <takashima.youichi@lab.ntt.co.jp>
  314. Patrick Ladd <Pat_Ladd2@cable.comcast.com>
  315. Norifumi Kikkawa <norifumi.kikkawa@jp.sony.com>
  316. Billy Gregory <bgregory@paciellogroup.com>
  317. Hanrui Gao <gaohanrui@360.cn>
  318. Hao Jing <jh.jinghao@huawei.com>
  319. Glenn Deen <glenn.deen@nbcuni.com>
  320. Lei Wang <wanglei@baidu.com>
  321. Tom Handal <thandal@verimatrix.com>
  322. Tsutomu Ogasawara <tsutomu.ogasawara@mail.rakuten.com>
  323. Jose Segura <jose.segura@mail.rakuten.com>
  324. Pengcheng Guo <guopengcheng@baidu.com>
  325. Erika Doyle Navara <erika.doyle@microsoft.com>
  326. Tom Wiltzius <wiltzius@google.com>
  327. Pierre-Anthony Lemieux <pal@sandflow.com>
  328. Xie Jianhui <xiejianhui@baidu.com>
  329. Yujie Jiang <jiangyujie@baidu.com>
  330. Leslie Sikos <sikos@sikoswebconsulting.com.au>
  331. David Newton <david@davidnewton.ca>
  332. Mark Sadecki <mark.sadecki+w3c@gmail.com>
  333. Kazuhiko Takabayashi <kazuhiko.takabayashi@jp.sony.com>
  334. Brady Eidson <beidson@apple.com>
  335. Reimundo Garcia <reimundo.garcia@hbo.com>
  336. Jerry Smith <jdsmith@microsoft.com>
  337. Michael Thornburgh <mthornbu@adobe.com>
  338. Cyril Rickelton-Abdi <cyril.rickelton-abdi@turner.com>
  339. Andrew Davis <papyromancer@gmail.com>
  340. Mick Hakobyan <mhakobyan@netflix.com>
  341. Angela Ricci <contact@thecodeplayground.net>
  342. Mallory van Achterberg <stommepoes@stommepoes.nl>
  343. Vladimir Sinelnikov <sinelnikov@gmail.com>
  344. Chris Wong <huanghoujin@baidu.com>
  345. Yiliang LIU <liuyiliang@baidu.com>
  346. David Sleight <hello@stuntbox.com>
  347. Hernan Beati <hernanbeati@gmail.com>
  348. mingqiang zhang <imcnan@gmail.com>
  349. yubo zhou <zhouyubo@360.cn>
  350. Ben Barber <barberboy@gmail.com>
  351. Suzanne Taylor <Suzanne.Taylor@pearson.com>
  352. Grzegorz Babula <gbabula@gmail.com>
  353. xueliang fan <fanxueliang@baidu.com>
  354. Mikio Sasaki <Sasaki.Mikio@bc.MitsubishiElectric.co.jp>
  355. Niels Thorwirth <nthorwirth@verimatrix.com>
  356. David Evans <david.evans@rd.bbc.co.uk>
  357. Danny O'Brien <danny@eff.org>
  358. Joseph Karr O'Connor <josephoconnor@mac.com>
  359. Vanessa Me Tonini <vanessa@nic.br>
  360. Seth Schoen <schoen@eff.org>
  361. Jamil Ellis <jamil.ellis@hbo.com>
  362. Jim Walsh <jim@jwalshcreative.com>
  363. Greg Davis <greg.davis@pearson.com>
  364. Gabino Alonso <gabinovincent@gmail.com>
  365. Sam Langdon <sam.langdon@hachette.co.uk>
  366. Michael Kelly <mkelly@mozilla.com>
  367. Xiaoqian Wu <xiaoqian@w3.org>
  368. Yue Min <minyue@baidu.com>
  369. Min Li <limin04@baidu.com>
  370. Mark Boyle <boyle.mr@gmail.com>
  371. A.S. Krishnakumar <ask@avaya.com>
  372. Shijun Sun <shijuns@microsoft.com>
  373. Jonathan Neal <jonathantneal@gmail.com>
  374. Joanmarie Diggs <jdiggs@igalia.com>
  375. Kei Gomita <Gomita.Kei@db.MitsubishiElectric.co.jp>
  376. Pedro Xavier Jorge <pedro.xavierjorge@gmail.com>
  377. diyar naozary <diyar.naozary@yahoo.com>
  378. Akira Torii <Torii.Akira@bp.MitsubishiElectric.co.jp>
  379. Tetsushi Matsuda <Matsuda.Tetsushi@dh.MitsubishiElectric.co.jp>
  380. So Vang <svang@nab.org>
  381. Flavio Yanai <yanai@nic.br>
  382. Ben Peters <ben.peters@microsoft.com>
  383. Amy Brown <hello@amybrowndesign.com>
  384. Nathalia Sautchuk Patrício <nathalia@nic.br>
  385. Deblyn prado <deblyn@nic.br>
  386. Vicente García Díaz <vicegd@live.com>
  387. Nan Jiang <ayajiang@hotmail.com>
  388. Nolan Butcher <nolan.butcher@hbo.com>
  389. Shinya Maruyama <Shinya.Maruyama@jp.sony.com>
  390. RAVI CHANDRA RAVULAPATI <ravichandra480@gmail.com>
  391. Yusuke Yokosuka <Yokosuka.Yusuke@bx.MitsubishiElectric.co.jp>
  392. John Riviello <john_riviello@comcast.com>
  393. Shun-ichi Sekiguchi <Sekiguchi.Shunichi@eb.MitsubishiElectric.co.jp>
  394. Glenn Eguchi <geguchi@adobe.com>
  395. Hirofumi Nishikawa <Nishikawa.Hirofumi@cs.MitsubishiElectric.co.jp>
  396. Hiroyuki Yamada <Yamada.Hiroyuki@dn.MitsubishiElectric.co.jp>
  397. Chockalingam Muthian <chockam@gmail.com>
  398. Michelangelo De Simone <michelangelo.de-simone@nokia.com>
  399. Lukáš Čihák <lukas.cihak@mensa.cz>
  400. Anatoly Shikolay <shikolay@gmail.com>
  401. WOOGLAE KIM <wlkim@inswave.com>
  402. Min Ren <minren@tencent.com>
  403. Rustam Khashimkhodjaev <Rustam_Khashimkhodjaev@cable.comcast.com>
  404. Brian Evans <Brian.Evans@microsoft.com>
  405. Jason White <jjwhite@ets.org>

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


Completed and maintained by Dominique Hazaël-Massieux (dom@w3.org) on an original design by Michael Sperberg-McQueen $Id: showv.php3,v 1.124 2014-10-06 13:46:23 dom Exp $. Please send bug reports and request for enhancements to dom@w3.org with w3t-sys@w3.org copied (if your mail client supports it, send mail directly to the right persons)