W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > December 2011

[Bug 12834] LEGEND should be allowed to NOT be exactly first child of FIELDSET ("The legend element" spec section)

From: <bugzilla@jessica.w3.org>
Date: Sun, 04 Dec 2011 08:48:21 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RX7kD-0004q1-1A@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12834

Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bhawkeslewis@googlemail.com

--- Comment #17 from Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> 2011-12-04 08:48:19 UTC ---
(In reply to comment #16)
> (In reply to comment #15) 
> Though, if it's needed, here is a bunch of testcases:
> http://tanalin.com/_experimentz/bugs/w3/html/wrap-legend/

What are you hoping user agents for blind and high magnification users will do
with these bits of extra text? What are their semantics? It's traditionally
been a bad idea to place text in forms that is not associated to a
field/control using a defined relationship (e.g. <label>, <legend>, @title,
@aria-labelledby, @aria-describedby, etc.), since otherwise the user might miss
the text when tabbing through the fields/controls of the form.

-- 
Configure bugmail: https://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 Sunday, 4 December 2011 08:48:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:02:09 UTC