- From: <bugzilla@jessica.w3.org>
- Date: Sun, 07 Jul 2013 07:45:56 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22586 --- Comment #15 from steve faulkner <faulkner.steve@gmail.com> --- (In reply to comment #14) > (In reply to comment #12) > > <label id="label1" for="f3">label text </label> > > <input type="text" id="f3" aria-labelledby="label1 label2 label3"> > > <p>other content</p> > > <label id="label2">more label text</label> > > <p>other content</p> > > <label id="label3">even more label text</label> > > So that example would not be valid if we were to change the spec to say a > <label> element must have either a "for" attribute or a "labelable elementa" > as a descendant. > > I recognize that the "aria-labelledby" attribute on the <input> element in > the example achieves a similar purpose, but I'm personally reluctant to > start making any core document-conformance rules change depending on > particular ARIA attributes, and I think it'd not unreasonable to consider it > a layering violation. can you provide more detail on the reasons for you personal reluctance and what the term 'layering violation' means a pointer to where it is defined would be especially helpful. What are the negative effects of allowing document conformance rules dependent on the presence of particular aria attributes? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Sunday, 7 July 2013 07:45:58 UTC