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

[Bug 12243] Warn when ARIA-describedby/-labelledby points to interactive/form associated content

From: <bugzilla@jessica.w3.org>
Date: Sat, 23 Apr 2011 00:38:23 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QDQrf-0002SO-D7@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12243

--- Comment #11 from Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no> 2011-04-23 00:38:22 UTC ---
(In reply to comment #10)
> First, section 5.2.7.3 describes how to calculate a text alternative, not a
> description which is what aria-describedby is. Section 5.2.7.2 is what
> describes how to get a description and only says:
> 
> "An accessible description may be computed by concatenating the text
> alternatives for nodes referenced by an aria-describedby ... outlined below in
> the section titled Text Alternative Computation"
> 
> So I see no requirements on that that is how it must be done. In other words, I
> see no requirement that methods that produce more semantically rich
> descriptions can't be used.

Quoting your quote:

  "outlined below in the section titled Text Alternative Computation"

'Text Alternative Computation' is the section I spoke about.  First point in
the Text alternative computation mentions both aria-labelledby and
aria-describedby:

" 1. Skip hidden elements unless the author specifies to use them via an
aria-labelledby or aria-describedby [snip]"

But I agre with you a little bit that aria-describedby is not as well described
as aria-labelledby. (But then, I also think that they could have been more
clear about @alt.)

> Second, where does section 5.2.7.2 say to only use the text contents of the
> elements?
> 
> Third bullet in step 2.A says
> 
> "Check for the presence of an equivalent host language attribute or element for
> associating a label, and use those mechanisms to determine a text alternative".
> Hence it says to use the native semantics of the elements unless overridden by
> aria- attributes by the earlier two bullets.

It says to use the native semantics for a specific purpose: "to determine a
text alternative". And the example it gives is @alt (which is just the host
language variant for aria-label).

Step 2C should be very relevant to you, as it speaks about collecting text from
elements:

"2C Otherwise [snip] text is collected from descendant content [snip]. The text
alternatives for child nodes will be concatenated [snip]"

This the wording "will be concatenated" tells to me that the elemetns will
presented as text.

-- 
Configure bugmail: http://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 Saturday, 23 April 2011 00:38:25 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:08 UTC