This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 12728 - This is not the proper WG for this document
Summary: This is not the proper WG for this document
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 alt techniques (editor: Steven Faulkner) (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: steve faulkner
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y
Depends on:
Blocks:
 
Reported: 2011-05-23 21:12 UTC by Sam Ruby
Modified: 2011-08-04 05:08 UTC (History)
8 users (show)

See Also:

Attachments

Description Sam Ruby 2011-05-23 21:12:18 UTC 
Bug entered on behalf of Janina Sajka:

This document was created to teach this WG about alt--because
earlier HTML spec drafts were so woefully wrong in how alt was
being specified. And, now this group is to be the expert on
what constitutes appropriate alternative text representations?
This is not the proper WG for this document, niehter at the current
time nor in the future as maintanance on it will be needed.

---

http://lists.w3.org/Archives/Public/www-archive/2011May/0052.html
Comment 1 steve faulkner 2011-06-03 11:11:03 UTC 
The argument that due to its content this document is being developed in the wrong working group must also be applied to the parts of the HTML5 specification that outline advice and requirements for the provision of text alternatives, as HTML5 contains similar requirements and advice. 
As long as the HTML5 specification contains such content, the right place for the alt spec is this working group. There is no obvious impediment to it's further development and maintenance by interested parties in the WAI just because it is being developed and maintained as a HTML working group product.
Comment 2 Sam Ruby 2011-06-03 17:36:27 UTC 
Janina, as this has been RESOLVED WORKSFORME, I encourage you to either:

a) Mark this as TrackerIssue so that we can proceed to call for proposals.

b) Voluntarily withdraw the corresponding Formal Objection.
Comment 3 Michael[tm] Smith 2011-08-04 05:08:39 UTC 
mass-move component to LC1