- From: Sam Ruby <rubys@intertwingly.net>
- Date: Tue, 03 Feb 2009 17:05:15 -0500
- To: Philip Taylor <pjt47@cam.ac.uk>
- CC: Larry Masinter <masinter@adobe.com>, HTML WG <public-html@w3.org>
Philip Taylor wrote: > > Larry Masinter wrote: >> [...] >> The proposal is to remove an accessibility-related attribute, without >> offering a replacement for its use, with no explanation except they >> looked at the Google index and figured they could axe it. > > That seems to be misrepresenting the position that has resulted in the > summary attribute not being in the HTML5 draft. I'm late to the party, but reading the following link, it does appear to be a misrepresentation. In general, drawing conclusions and inferring motivation without doing the proper research isn't the best way to start an open discussion. > See http://lists.w3.org/Archives/Public/public-html/2008Dec/0175.html > for a summary of various issues. Restoring a bit of context from Larry's original e-mail: > The unanimous position of PF and WAI on @summary is that it's needed. > > http://esw.w3.org/topic/HTML/SummaryForTABLE Scanning both links, it seems relatively likely to me that the HTML5 working group considered the points raised on the PFWG link; and it seems less likely to me that the PFWG considered the points raised in the HTML5 link, but that could be my ignorance. Even without fully understanding the issue, it is clear that this issue has been going on for quite some time, and I infer from that that it is likely that it won't be resolved quickly. Larry: it might be useful to write up a short statement (ideally a balanced one that covers both positions, if that's humanly possible) to be included in the draft for now? If it doesn't get resolved by then (and I have a sneaking suspicion that it won't), this could be good fodder for discussion at the AC meeting next month. - Sam Ruby
Received on Tuesday, 3 February 2009 22:05:48 UTC