W3C home > Mailing lists > Public > public-html-a11y@w3.org > January 2012

FW: ISSUE-200: legend-placement - Chairs Solicit Proposals

From: Cynthia Shelly <cyns@microsoft.com>
Date: Tue, 17 Jan 2012 22:09:21 +0000
To: "public-html-a11y@w3.org" <public-html-a11y@w3.org>
Message-ID: <C7E43C8B2FFAC740A28B5E52CF7EA9191153538E@TK5EX14MBXC293.redmond.corp.microsoft.com>
I think we should support this change.  Removing the first-child requirement makes it easier to use <legend> in more layouts, which means that <legend> might get used more.  I wonder if it would make sense to add <legend for> that works the same way as <lable for>?

-----Original Message-----
From: Paul Cotton [mailto:Paul.Cotton@microsoft.com] 
Sent: Tuesday, January 17, 2012 6:49 AM
To: public-html@w3.org
Subject: ISSUE-200: legend-placement - Chairs Solicit Proposals

'Allow wrapping LEGEND (or new iLEGEND) in non-FIELDSET elements'
 
Per the HTML WG Decision Policy, at this time the chairs would like to solicit volunteers to write Change Proposals for ISSUE-200:
 
http://www.w3.org/html/wg/tracker/issues/200     
http://dev.w3.org/html5/decision-policy/decision-policy.html#escalation
 
If no Change Proposals are written by February 16th, 2012, this issue will be closed without prejudice.
 
Issue status link:
http://dev.w3.org/html5/status/issue-status.html#ISSUE-200 

/paulc
HTML WG co-chair

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (425) 705-9596 Fax: (425) 936-7329
Received on Tuesday, 17 January 2012 22:09:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:52 GMT