[Bug 18744] drop WAI-ARIA scope restriction in the text adopted in ISSUE-204

https://www.w3.org/Bugs/Public/show_bug.cgi?id=18744

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

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

--- Comment #19 from Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> 2012-09-09 21:41:26 UTC ---
(In reply to comment #15)
> 2) <label> has the ID association backwards; the auxiliary label/description
> references the content rather than the other way around. So that makes it
> unlike any of the other cases we are thinking about. I think there's a
> difference between letting references point to hidden elements and letting
> hidden elements create references. For example, you might have multiple labels
> pointing to the same control and hide all but the currently relevant one.

Doubt the direction of the reference makes any difference here.

You might have the same control referencing multiple descriptions and hide all
but the currently relevant one, and in fact authors try to do this:

http://www.nvda-project.org/ticket/2597

Previously brought to the WG's attention:

http://lists.w3.org/Archives/Public/public-html/2012Aug/0212.html

> 3) Historically, it appears that hidden or display:none labels are not
> presented at all by assistive technologies, at least in my testing. So the
> change wouldn't just be flattened to structured, it would be not presenting to
> presenting.

Are you suggesting that <label for> should have the implicit semantics of
@aria-labelledby but not when the label element is hidden with @hidden or
display: none?

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Received on Sunday, 9 September 2012 21:41:27 UTC