Skip to content

3.1.2 Language of Parts - Computed acc name clarification + ambiguous example #4423

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.

Sign up for GitHub

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

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open

3.1.2 Language of Parts - Computed acc name clarification + ambiguous example #4423

Changes from 1 commit
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
13024ba
Update language-of-parts.html
giacomo-petri Jun 3, 2025
c43c4ab
removed redundancy
giacomo-petri Jun 3, 2025
5ee62bb
missing example
giacomo-petri Jun 3, 2025
299d9a6
html adjustment
giacomo-petri Jun 3, 2025
b73f4f7
Update language-of-parts.html
giacomo-petri Jun 3, 2025
b37038a
Update language-of-parts.html
giacomo-petri Jun 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
html adjustment
  • Loading branch information
@giacomo-petri
giacomo-petri authored Jun 3, 2025
commit 299d9a6aaf3265887c207dc2fad4be4f52d2a78b
4 changes: 2 additions & 2 deletions understanding/20/language-of-parts.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -145,9 +145,9 @@ <h3>Alternative language links</h3>
<h3>Element's content used as accessible name</h3>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd preface this section with a preamble about the limitation of current assistive technologies in handling changes of language as part of their accessible name calculation. Explaining that while theoretically correct, switching language inside the accname is not currently supported. This then leads into the first example as simple mitigation.

Would be interested to know if this issue just happens in forms mode or also in browse mode? Does it also affect accessible description? Any other scenarios?

in the second example, you're technically not "setting" the parent element to the primary language ... you're letting it inherit the language from the document's overall language. and it's perhaps not that this is "acceptable", but rather that it's still required to do so (but being aware that AT may not switch language when announcing the link).

<p>When content is used as the accessible name of an element, the correct language should be specified on that element. This helps assistive technologies pronounce it accurately.</p>
<p>This link may be announced with an English accent, mispronouncing "Español".</p>
<pre xml:space="preserve"><code class="language-html">&lt;a href="/es/"&gt;&lt;span lang="es"&gt;Español&lt;/span&gt;&lt;/a&gt;</code></pre>
<p><code class="language-html"><code class="language-html">&lt;a href="/es/"&gt;&lt;span lang="es"&gt;Español&lt;/span&gt;&lt;/a&gt;</code></p>
<p>This version correctly applies the Spanish language to the element, ensuring "Español" is pronounced with a Spanish accent.</p>
<pre xml:space="preserve"><code class="language-html">&lt;a href="/es/" lang="es"&gt;&lt;span&gt;Español&lt;/span&gt;&lt;/a&gt;</code></pre>
<p><code class="language-html"><code class="language-html">&lt;a href="/es/" lang="es"&gt;&lt;span&gt;Español&lt;/span&gt;&lt;/a&gt;</code></p>

<h3>Element's content in multiple languages used as accessible name</h3>
<p>When content includes multiple languages, it's acceptable to set the parent element to the primary language, as long as any child elements in a different language have the appropriate language set.</p>
Expand Down