Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarification on 3.1.2 Language of Parts #297

Closed
goodwitch opened this issue Jul 24, 2017 · 10 comments · Fixed by #808
Closed

Clarification on 3.1.2 Language of Parts #297

goodwitch opened this issue Jul 24, 2017 · 10 comments · Fixed by #808

Comments

@goodwitch
Copy link
Contributor

So, I need clarification on 3.1.2 Language of Parts

Is it a failure if

  • (an html web site has alternative language links to versions of the page in other languages (e.g., Deutsch, Français, Nederlands, Castellano, etc.)) AND
  • (the text of each link is the name of the language, in that language) AND
  • (the language of each link is indicated via a lang attribute) AND
  • (the text of each language link does not have a language attribute to indicate the change in language?

Why am I asking this question? Because I've been calling this as a failure...but one of my colleagues just pointed out that the normative part of this SC says "passage or phrase", so they tell me, that since these language links are single words, they are not required to be marked.

My brain says...sometimes a phrase can be a single word. And I've found evidence of this in linguistics.

If you agree that this is a failure, would it be worthwhile to add this as a failure technique for 3.1.2 in WCAG 2.0?

Thanks for considering this.

@Ryladog
Copy link

Ryladog commented Jul 24, 2017 via email

@srinivasuchakravarthula
Copy link

@KerstinProbiesch
Copy link
Contributor

@goodwitch, all,

this example is mentioned in the Understanding of SC 3.1.2 (Example 2). So it seems that a single word can be seen as a "phrase". But because there is no definition of "phrase" in the glossary it's not very lucky when just the informative understanding document indicates this. That's why I filed an issue for WCAG 2.1 that a "definition of phrase in the glossary is needed": w3c/wcag21#287.

In some german texts about this aspect it is said that of course it is a benefit and a must when correct lang-attributes for longer passages of texts have been used. But it is also written that the benefit for single words is lower and can also be disturbing when many single words with lang-attribute are present because of a short pause in the reading flow of JAWS when switching in the other language and back. (Of course the SC says that not every single word of another language must be defined). This pause in the reading flow seems to be nowadays in comparison with ten years ago shorter but seems to be still there.

I think one aspect is: As far as I know english speaking people tend to pronounce words from other languages with english pronounciation (for example "kindergarten") and the amount of words from other languages seems to be not so high than in other languages. In comparison with english the amount of words from other languages in german texts for example is in general much higher and we tend to pronounce for example english words in english.

I think that a failure technique with some examples would be very helpful to bring in more clarification in SC 3.1.2. And I also think that the Working Group should seek for feedback on this issue / future failure techniques especially from screenreader user from countries where english is not native language.

@Ryladog
Copy link

Ryladog commented Jul 25, 2017 via email

@alastc
Copy link
Contributor

alastc commented Jun 28, 2019

Hi everyone, I'm going through old issues...
For the scenario where you have a link to another page with the name of the language in the language (e.g. "Français"), the understanding doc has that example.

I wasn't worried by the use of "phrase", that could be a word.

I did wonder if you could consider Français a "proper name" for France? In which case you could exempt that... However I think that scenario of language links is fairly important to get right, for people who need that language to hear it pronounced properly.

Overall, does anyone want to sign up for creating a technique/failure for this?
If not, I suggest we defer or simply close this one.

@patrickhlauke
Copy link
Member

patrickhlauke commented Jun 28, 2019

I did wonder if you could consider Français a "proper name" for France

well, a proper name for "French" (in French). but i'd say no to the larger question. And that language links that just have a single word (the language, in that language) need lang or it's a failure.

<ul>
  <li><a href="..." lang="de">Deutsch</a></li>
  <li><a href="..." lang="it">Italiano</a></li>
  <li><a href="..." lang="fr">Français</a></li>
  ...
  <li><a href="..." lang="zh-hant">繁體中文</a></li>
</ul>

so, even though the SC talks about "phrase", even a single word can count here i'd say. (feel free to grab the above and just slot it into the understanding bullet point...or does that warrant its own separate technique document?)

@alastc
Copy link
Contributor

alastc commented Jun 28, 2019

I think the nub of this issue is clarifying that a phrase can be a word.

Maybe change the first line of the intent in the understanding doc to:

The intent of this Success Criterion is to ensure that user agents can correctly present words, phrases or passages written in multiple languages.

@cstrobbe
Copy link

My brain says...sometimes a phrase can be a single word. And I've found evidence of this in linguistics.

Yes, a single word can count as a phrase. To quote the definition of phrase from Wiktionary:

(grammar) A word or, more commonly, a group of words that functions as a single unit in the syntax of a sentence, usually consisting of a head, or central word, and elaborating words.

When I studied linguistics at university, one of the things I learnt was that there is no definition for "word" that works across languages. For this reason, the "ambiguity" of the term "phrase" can be seen as an advantage.

So I agree with other commenters that something like <li><a href="..." lang="fr">français</a></li> requires a lang attribute. (Names of languages are written in lowercase in French.)

@CharlesBelov
Copy link

See also 3.1.2 Language of parts - can single words without lang mark-up be considered a PASS? #1174

@awkawk
Copy link
Member

awkawk commented May 16, 2023

Also related to: w3c/wcag21#287

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

9 participants