E-mail List Archives
Re: [EXT] can you make a native <select>/<option> honor the LANG attribute?
From: wolfgang.berndorfer@zweiterblick.at
Date: Dec 18, 2020 9:27AM
- Next message: Steve Green: "Re: TOC Hyperlinks question"
- Previous message: Laura Fathauer: "Re: TOC Hyperlinks question"
- Next message in Thread: None
- Previous message in Thread: Jared Smith: "Re: [EXT] can you make a native
- View all messages in this Thread
A language change of synth within a page is really quite disrupting for me
too. But hearing a wrong pronunciation trains my brain to speak in wrong
pronunciation, as I personally experienced. It's good to have SR settings to
decide between plague and cholera.
-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
Birkir R. Gunnarsson
Sent: Thursday, December 17, 2020 11:05 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] [EXT] can you make a native <select>/<option> honor
the LANG attribute?
Ooh! I'm looking forward to that blog post!
Honestly, as a screen reader user (as opposed to an expert) I prefer to hear
the page with the same synth and turn of language detection on demand. Heck,
I'm even more comfortable reading Icelandic with an English TTS engine by
now, which is odd seeing as I actually helped create the Icelandic TTS
engine.
I find it really difficult to navigate multi-lingual pages where the screen
reader is constantly switching between TTS engines. With English I have at
least a vauge idea of what the words are. I'd be curious to hear what other
screen readerusers prefer.
On 12/17/20, Jared Smith < <EMAIL REMOVED> > wrote:
> I can confirm the same behavior on VoiceOver with Chrome and Safari,
> and VoiceOver mobile. VoiceOver does not change language when
> exploring the options, even if the proper <option lang> value is
> defined. It reads them all in English.
>
> Interestingly, VoiceOver mobile does (sometimes) properly read
> non-Latin words in their proper language, but this is because it's
> guessing based on the script of the characters, not because the lang
> attribute is being considered.
>
> We just today wrapped up some fairly extensive screen reader testing
> of lang attribute support and found this inconsistency to be fairly
standard.
> Several screen readers do not support inline language changes
> ("language of
> parts") for inline elements (<span>, etc.), but does for block-level
> elements (<p>, <div>, etc.). It seems <option> aligns with the former.
> A list of links, or perhaps a custom menu (such as on UPS) is probably
> a better alternative until these deficiencies are addressed.
>
> WebAIM will very soon be publishing a new article with guidance on
> using lang. I'll share our test cases and testing results at that time.
>
> Thanks,
>
> Jared
>
>
> > > archives at http://webaim.org/discussion/archives
> >
--
Work hard. Have fun. Make history.
http://webaim.org/discussion/archives
- Next message: Steve Green: "Re: TOC Hyperlinks question"
- Previous message: Laura Fathauer: "Re: TOC Hyperlinks question"
- Next message in Thread: None
- Previous message in Thread: Jared Smith: "Re: [EXT] can you make a native
- View all messages in this Thread