W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > September 2010

[Bug 10455] Mint a describedby attribute for the img element

From: <bugzilla@jessica.w3.org>
Date: Thu, 02 Sep 2010 21:29:39 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1OrHLn-0003Kb-H9@jessica.w3.org>

--- Comment #74 from Gregory J. Rosmaita <oedipus@hicom.net>  2010-09-02 21:29:36 ---
in reply to comment #71

benjamin -- i for one would very much welcome more and varied participation in
the HTML A11y TF, especially yours, as i have found your work for the WG to be
consistently thorough...

re-checking the TF's work statement, located at:


i found the following:

Members of the public who are not covered by the W3C Patent Policy can send
input to the public-pfwg-comments mailing list [public-pfwg-comments archive],
or the public-html-comments mailing list [public-html-comments archive].
Messages should clearly indicate the deliverable to which they are related and
that they are relevant to the work of the HTML Accessibility Task Force.

since this has been a question that has arisen before (how to submit comments
so that they are efficiently and expeditiously brought to the attention of the
HTML Accessibility Task Force's members and facilitators) would it be possible
for the chairs to speak on this issue, as:

1. there are already too many HTML5-centric lists to which one can post; how
best to funnel feedback directly to the A11y TF needs to be determined by the
chairs, as the public-html-a11y@w3.org list is publicly viewable, but one
cannot -- as you pointed out -- post to it if one isn't already subscribed to

2. the severe limitations of bugzilla -- in the case of this bug, like so many
others, without headers to mark the beginning of individual comments,
everything after the FORM-stuffed-in-a-TABLE appears as undifferentiated text,
making it difficult to navigate what not only constitutes the "meat of the
matter" but also comprises the vast bulk of the information contained in the
bug report without recourse to copying-and-pasting the complete bug report into
a plain text editor (which is obviously less-than-optimal, as one is then
forced to work on a snapshot of the bug report, rather than working with a
document that may be updated during the composition of a comment

therefore, should accessibility inquiries, comments, questions and suggestions
be funneled to the HTML A11y TF via public-pfwg-comments@w3.org ?

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 2 September 2010 21:29:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:24 UTC