W3C

Results of Questionnaire Call for Consensus on proposed tests for the HTML5 Image Description Extension

The results of this questionnaire are available to anybody.

This questionnaire was open from 2013-09-24 to 2013-10-03.

3 answers have been received.

Jump to results for question:

  1. Longdesc value as data:URI for an image that is a data:URI
  2. Longdesc value as data:URI for an empty image
  3. Longdesc value as data:URI (surrounded by whitespace) for an external image
  4. Longdesc value as data:URI for an external image
  5. Longdesc value as external URI for an image that is a data:URI
  6. Longdesc value as external URI for an empty image
  7. Longdesc value as external URI (surrounded by whitespace) for an external image
  8. Longdesc value as external URI for an external image
  9. Longdesc value as internal URI for an image that is a data:URI
  10. Longdesc value as internal URI for an empty image
  11. Longdesc value as internal URI (surrounded by whitespace) for an external image
  12. Longdesc value as internal URI for an external image
  13. Longdesc value as fragment in an external URI for an image that is a data:URI
  14. Longdesc value as fragment in an external URI for an empty image
  15. Longdesc value as fragment in an external URI (surrounded by whitespace) for an external image
  16. Longdesc value as fragment in an external URI for an external image
  17. Longdesc value as external URI for an external image. Page has relative <base> element.
  18. Longdesc value as external URI for an external image. Page has absolute <base> element.
  19. Longdesc value as external URI for an image in an <iframe>
  20. Longdesc value updated by javascript
  21. Invalid long description (plain text)
  22. Invalid long description (empty attribute)
  23. Pointer to an invalid long description (not contained in a well-formed fragment)

1. Longdesc value as data:URI for an image that is a data:URI

Please indicate if the test below sufficiently demonstrates support for a longdesc which uses a data:URI as its value for an image that uses a data:URI as its value:

Summary

ChoiceAll responders
Results
yes 3
no
concur
abstain

Details

Responder Longdesc value as data:URI for an image that is a data:URIRationale
Mark Sadecki yes
David MacDonald yes
Charles 'chaals' (McCathie) Nevile yes

2. Longdesc value as data:URI for an empty image

Please indicate if the test below sufficiently demonstrates support for a longdesc which uses a data:URI as its value for an image that lacks a src attribute value:

Summary

ChoiceAll responders
Results
yes 3
no
concur
abstain

Details

Responder Longdesc value as data:URI for an empty imageRationale
Mark Sadecki yes
David MacDonald yes
Charles 'chaals' (McCathie) Nevile yes

3. Longdesc value as data:URI (surrounded by whitespace) for an external image

Please indicate if the test below sufficiently demonstrates support for a longdesc which uses a data:URI that is surrounded by whitespace as its value for an external image:

Summary

ChoiceAll responders
Results
yes 3
no
concur
abstain

Details

Responder Longdesc value as data:URI (surrounded by whitespace) for an external imageRationale
Mark Sadecki yes
David MacDonald yes
Charles 'chaals' (McCathie) Nevile yes

4. Longdesc value as data:URI for an external image

Please indicate if the test below sufficiently demonstrates support for a longdesc which uses a data:URI as its value for an external image:

Summary

ChoiceAll responders
Results
yes 3
no
concur
abstain

Details

Responder Longdesc value as data:URI for an external imageRationale
Mark Sadecki yes
David MacDonald yes
Charles 'chaals' (McCathie) Nevile yes

5. Longdesc value as external URI for an image that is a data:URI

Please indicate if the test below sufficiently demonstrates support for a longdesc which uses an external URI as its value for an an image that uses a data:URI as its value:

Summary

ChoiceAll responders
Results
yes 3
no
concur
abstain

Details

Responder Longdesc value as external URI for an image that is a data:URIRationale
Mark Sadecki yes
David MacDonald yes
Charles 'chaals' (McCathie) Nevile yes

6. Longdesc value as external URI for an empty image

Please indicate if the test below sufficiently demonstrates support for a longdesc which uses an external URI as its value for an image that lacks a src attribute value:

Summary

ChoiceAll responders
Results
yes 3
no
concur
abstain

Details

Responder Longdesc value as external URI for an empty imageRationale
Mark Sadecki yes
David MacDonald yes
Charles 'chaals' (McCathie) Nevile yes

7. Longdesc value as external URI (surrounded by whitespace) for an external image

Please indicate if the test below sufficiently demonstrates support for a longdesc which uses an external URI surrounded by whitespace as its value for an external image:

Summary

ChoiceAll responders
Results
yes 3
no
concur
abstain

Details

Responder Longdesc value as external URI (surrounded by whitespace) for an external imageRationale
Mark Sadecki yes
David MacDonald yes
Charles 'chaals' (McCathie) Nevile yes

8. Longdesc value as external URI for an external image

Please indicate if the test below sufficiently demonstrates support for a longdesc which uses an external URI as its value for an external image:

Summary

ChoiceAll responders
Results
yes 3
no
concur
abstain

Details

Responder Longdesc value as external URI for an external imageRationale
Mark Sadecki yes
David MacDonald yes
Charles 'chaals' (McCathie) Nevile yes

9. Longdesc value as internal URI for an image that is a data:URI

Please indicate if the test below sufficiently demonstrates support for a longdesc which uses an internal URI as its value for an image that is a data:URI as its value:

Summary

ChoiceAll responders
Results
yes 3
no
concur
abstain

Details

Responder Longdesc value as internal URI for an image that is a data:URIRationale
Mark Sadecki yes
David MacDonald yes
Charles 'chaals' (McCathie) Nevile yes

10. Longdesc value as internal URI for an empty image

Please indicate if the test below sufficiently demonstrates support for a longdesc which uses an internal URI as its value for an image that lacks a src attribute value:

Summary

ChoiceAll responders
Results
yes 3
no
concur
abstain

Details

Responder Longdesc value as internal URI for an empty imageRationale
Mark Sadecki yes
David MacDonald yes
Charles 'chaals' (McCathie) Nevile yes

11. Longdesc value as internal URI (surrounded by whitespace) for an external image

Please indicate if the test below sufficiently demonstrates support for a longdesc which uses an internal URI surrounded by whitespace as its value for an external image:

Summary

ChoiceAll responders
Results
yes 3
no
concur
abstain

Details

Responder Longdesc value as internal URI (surrounded by whitespace) for an external imageRationale
Mark Sadecki yes
David MacDonald yes
Charles 'chaals' (McCathie) Nevile yes

12. Longdesc value as internal URI for an external image

Please indicate if the test below sufficiently demonstrates support for a longdesc which uses an internal URI as its value for an external image:

Summary

ChoiceAll responders
Results
yes 3
no
concur
abstain

Details

Responder Longdesc value as internal URI for an external imageRationale
Mark Sadecki yes
David MacDonald yes
Charles 'chaals' (McCathie) Nevile yes

13. Longdesc value as fragment in an external URI for an image that is a data:URI

Please indicate if the test below sufficiently demonstrates support for a longdesc which uses a fragment or id reference in an external URI as its value for an image that uses a data:URI as its value:

Summary

ChoiceAll responders
Results
yes 3
no
concur
abstain

Details

Responder Longdesc value as fragment in an external URI for an image that is a data:URIRationale
Mark Sadecki yes
David MacDonald yes
Charles 'chaals' (McCathie) Nevile yes

14. Longdesc value as fragment in an external URI for an empty image

Please indicate if the test below sufficiently demonstrates support for a longdesc which uses a fragment or id reference in an external URI as its value for an image that lacks a src attribute value:

Summary

ChoiceAll responders
Results
yes 3
no
concur
abstain

Details

Responder Longdesc value as fragment in an external URI for an empty imageRationale
Mark Sadecki yes
David MacDonald yes
Charles 'chaals' (McCathie) Nevile yes

15. Longdesc value as fragment in an external URI (surrounded by whitespace) for an external image

Please indicate if the test below sufficiently demonstrates support for a longdesc which uses a fragment or id reference in an external URI, surrounded by whitespace, as its value for an external image:

Summary

ChoiceAll responders
Results
yes 3
no
concur
abstain

Details

Responder Longdesc value as fragment in an external URI (surrounded by whitespace) for an external imageRationale
Mark Sadecki yes
David MacDonald yes
Charles 'chaals' (McCathie) Nevile yes

16. Longdesc value as fragment in an external URI for an external image

Please indicate if the test below sufficiently demonstrates support for a longdesc which uses a fragment or id reference in an external URI as its value for an external image:

Summary

ChoiceAll responders
Results
yes 3
no
concur
abstain

Details

Responder Longdesc value as fragment in an external URI for an external imageRationale
Mark Sadecki yes
David MacDonald yes
Charles 'chaals' (McCathie) Nevile yes

17. Longdesc value as external URI for an external image. Page has relative <base> element.

Please indicate if the test below sufficiently demonstrates support for a longdesc which uses an external URI for an external image. The document has an absolute <base> element:

Summary

ChoiceAll responders
Results
yes 3
no
concur
abstain

Details

Responder Longdesc value as external URI for an external image. Page has relative &lt;base&gt; element.Rationale
Mark Sadecki yes
David MacDonald yes
Charles 'chaals' (McCathie) Nevile yes

18. Longdesc value as external URI for an external image. Page has absolute &lt;base&gt; element.

Please indicate if the test below sufficiently demonstrates support for a longdesc which uses an external URI for an external image. The document has an absolute <base> element:

Summary

ChoiceAll responders
Results
yes 3
no
concur
abstain

Details

Responder Longdesc value as external URI for an external image. Page has absolute &lt;base&gt; element.Rationale
Mark Sadecki yes
David MacDonald yes
Charles 'chaals' (McCathie) Nevile yes

19. Longdesc value as external URI for an image in an &lt;iframe&gt;

Please indicate if the test below sufficiently demonstrates support for a longdesc which uses an external URI for an image contained in an <iframe>:

Summary

ChoiceAll responders
Results
yes 3
no
concur
abstain

Details

Responder Longdesc value as external URI for an image in an &lt;iframe&gt;Rationale
Mark Sadecki yes
David MacDonald yes
Charles 'chaals' (McCathie) Nevile yes

20. Longdesc value updated by javascript

Please indicate if the test below sufficiently demonstrates that the HTML attribute reflects changes made by javascript:

NOTE: To pass this test, the browser must redirect to the "Longdesc test Pass Page" which has the word "Pass" as a heading, followed by a description of the image. Displaying the "Longdesc test Fail Page" would indicate a failure of this test.

Summary

ChoiceAll responders
Results
yes 3
no
concur
abstain

Details

Responder Longdesc value updated by javascriptRationale
Mark Sadecki yes
David MacDonald yes
Charles 'chaals' (McCathie) Nevile yes

21. Invalid long description (plain text)

Please indicate if the test below sufficiently demonstrates an invalid long description (contains plain text and not a URI) and can be used to test User Agent and validation tool handling:

NOTE: Handling of invalid longdesc by user agents is currently undefined.

Summary

ChoiceAll responders
Results
yes 3
no
concur
abstain

Details

Responder Invalid long description (plain text)Rationale
Mark Sadecki yes
David MacDonald yes
Charles 'chaals' (McCathie) Nevile yes

22. Invalid long description (empty attribute)

Please indicate if the test below sufficiently demonstrates an invalid long description (has an empty or null value) and can be used to test User Agent and validation tool handling:

NOTE: Handling of invalid longdesc by user agents is currently undefined.

Summary

ChoiceAll responders
Results
yes 3
no
concur
abstain

Details

Responder Invalid long description (empty attribute)Rationale
Mark Sadecki yes
David MacDonald yes
Charles 'chaals' (McCathie) Nevile yes

23. Pointer to an invalid long description (not contained in a well-formed fragment)

Please indicate if the test below sufficiently demonstrates an invalid long description (points to a fragment in an empty element) and can be used to test User Agent and validation tool handling:

NOTE: Handling of invalid longdesc by user agents is currently undefined. Validation tools should at least generate a warning, since an empty element is almost certainly not an adequate description, and is likely instead to reflect not passing the relevant authoring requirement.

Summary

ChoiceAll responders
Results
yes 3
no
concur
abstain

Details

Responder Pointer to an invalid long description (not contained in a well-formed fragment) Rationale
Mark Sadecki yes
David MacDonald yes
Charles 'chaals' (McCathie) Nevile yes Note that I am not sure whether to say a tool that didn't point out the problem has actually failed, since it can only be done by relying on a heuristic analysis (although the test case is pretty unlikely not to be a failure...)

More details on responses

  • Mark Sadecki: last responded on 26, September 2013 at 13:44 (UTC)
  • David MacDonald: last responded on 26, September 2013 at 15:14 (UTC)
  • Charles 'chaals' (McCathie) Nevile: last responded on 27, September 2013 at 02:24 (UTC)

Everybody has responded to this questionnaire.


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.