WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: [EXT] can you make a native <select>/<option> honor the LANG attribute?


From: Michael Ausbun
Date: Dec 17, 2020 3:35PM

Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable

To be honest, I feel the same way. I've trained my brain to process certain=
pronunciations and other eccentricities at a specific speed, with a specif=
ic TTS engine. When small changes occur, productivity is drastically reduce=
d. Even very minor adjustments can result in processing issues for me.

Michael Duane Ausbun, MA, CPWA (He, His, Him)
Accessibility Specialist, Program Development,
Universal Design and Accessibility Team
Ruston, Louisiana

Western Governors University
4001 South 700 East, Suite 700
Salt Lake City, UT 84107

[IAAP CPWA small circular badge and horizontal name logo for International =
Association of Accessibility Professionals (IAAP) Certified Professional in=
Web Accessibility (CPWA) credential. To the left is a dark blue circle wit=
h three lines of centered white text that read: IAAP Certified CPWA. There =
is a smaller silver circle that surrounds the dark blue inner circle that d=
esignates the CPWA credential color scheme. To the right, three lines of da=
rk blue text. Top text reads Certified Professional, second line reads in W=
eb Accessibility, third line reads International Association of Accessibili=
ty Professionals.]<https://www.accessibilityassociation.org/cpwa>

[JAWS Certified, 2020]<http://www.freedomscientific.com/Certification>;

From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Birk=
ir R. Gunnarsson
Sent: Thursday, December 17, 2020 4:05 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] [EXT] can you make a native <select>/<option> honor t=
he LANG attribute?

[EXTERNAL EMAIL] WARNING: This email originated from outside of Western Gov=
ernors University.

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> <mailto: <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 o=
> 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 l=
> attribute support and found this inconsistency to be fairly standard.
> Several screen readers do not support inline language changes ("language =
> 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
> > baim.org>
> discussion/archives>
> @list.webaim.org>

Work hard. Have fun. Make history.

Content-Type: image/png; name="image001.png"
Content-Description: image001.png
Content-Disposition: inline; filename="image001.png"; size=212;
creation-date="Thu, 17 Dec 2020 22:35:45 GMT";
modification-date="Thu, 17 Dec 2020 22:35:45 GMT"
Content-ID: < <EMAIL REMOVED> 2FEE70>
Content-Transfer-Encoding: base64

Content-Type: image/png; name="image002.png"
Content-Description: image002.png
Content-Disposition: inline; filename="image002.png"; size=190;
creation-date="Thu, 17 Dec 2020 22:35:45 GMT";
modification-date="Thu, 17 Dec 2020 22:35:45 GMT"
Content-ID: < <EMAIL REMOVED> 2FEE70>
Content-Transfer-Encoding: base64