[Bug 23305] Allow the lang attribute to parse Alt and Title attributes in the selected language

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

Jukka K. Korpela <jukka.k.korpela@kolumbus.fi> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jukka.k.korpela@kolumbus.fi

--- Comment #3 from Jukka K. Korpela <jukka.k.korpela@kolumbus.fi> ---
The first sentence at 3.2.5.3 (The lang and xml:lang attributes) is: “The lang
attribute (in no namespace) specifies the primary language for the element's
contents and for any of the element's attributes that contain text.” I think
this clearly says that alt and title attributes are included. But I guess it
would not hurt to append “such as the alt and title attributes” to the
sentence.

It seems that the concept “attributes that contain text” is not defined
anywhere but is to be understood intuitively. And it is not quite clear what it
means. My intuitive interpretation was that it means any attribute with a value
that can be regarded as being in a human language. But on second thought, I
might be wrong. After all, class="nice little stuff" might be regarded as such
an attribute, but that’s not what is meant, of course.

So maybe the attributes affected should be explicitly listed, or the definition
of each attribute should specify whether its content is text (in the sense
meant here, as opposite to allowing any string as value). What would they be,
in addition to the obvious alt and title? Probably abbr, content (in some
cases), label, placeholder, and some obsolete attributes. But maybe the value
attribute, e.g. as in <input type=submit value="Subscribe">, should be included
– it’s something that should be spellchecked, translated if the page is
translated, and formatted using language-specific rules if relevant – and
processed in speech synthesis as being in a specific language.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 23 October 2013 06:21:36 UTC