- From: Sam Ruby <rubys@intertwingly.net>
- Date: Fri, 04 Jun 2010 16:58:18 -0400
- To: John Foliot <jfoliot@stanford.edu>
- CC: 'Laura Carlson' <laura.lee.carlson@gmail.com>, 'Shelley Powers' <shelleyp@burningbird.net>, 'HTML WG' <public-html@w3.org>, 'HTML Accessibility Task Force' <public-html-a11y@w3.org>
On 06/04/2010 04:37 PM, John Foliot wrote: > > The 'philosophical' decision to keep the element(s) mentioned in Issues 90& > 91 in HTML5 has been reached following W3C process. At this point, if a > *member of the Working Group* feels that there are 'issues' with aspects of > these elements, I would suspect that the appropriate next step would be to > file one or more bug reports against that element. However, the fundamental > decision or retaining or abandoning this element has been addressed, and the > decision has been made, and so any such bug report should focus on > 'remediation' rather than removal at this time (unless a clear technical > argument that demonstrates 'harm' is brought forth). Chairs, is this > correct? One doesn't need to be a member of the working group to file a bug, I would encourage everyone to participate. If you read the decisions[1][2] down to the final paragraph in each, all the decision ruled on is whether or not these elements are to be removed AT THIS TIME. If the implementations aren't forthcoming, these elements will be removed later in the process. If the a11y bugs that Shelley is expecting[3] do materialize, that may also trigger their removal. As would unresolvable issues of any other kind. A bug is a bug. Fixes may involve remediation or removal. I will agree, however, that those two options are likely to be pursued in that order, i.e., removal only if remediation fails. - Sam Ruby [1] http://lists.w3.org/Archives/Public/public-html/2010Jun/0002.html [2] http://lists.w3.org/Archives/Public/public-html/2010Jun/0003.html [3] http://lists.w3.org/Archives/Public/public-html/2010Jun/0077.html
Received on Friday, 4 June 2010 20:58:48 UTC