W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2017

Inline lang= Support [Was: Re: VoiceOver lang="" compatibility]

From: Janina Sajka <janina@rednote.net>
Date: Thu, 16 Nov 2017 10:34:05 -0500
To: w3c-wai-ig@w3.org
Message-ID: <20171116153405.GG23594@rednote.net>
This is something of a hobby horse with me, and I wonder ...  Is there
any OS/AT environment that reliably supports lang="" markup thoroughly?

By way of example I would note there's been quite a bit of activity and
interest on Android over the past year or so, but the approach that made
it into the Play Store app, AutoTTS,  was purely heuristic, not markup
based. That's arguably OK for clearly unrelated languages, e.g. Chinese
and Arabic, but not so for closely related language families, e.g.
English and German. I tried to use it and ultimately gave up.

The next version of Android Talkback, now in public beta,  has builtin
auto language switching. I haven't played with it myself yet and can't
say whether it's heuristic or markup based--or both.

I raise the distinction because I believe it's particularly important to
have markup based language switching well supported. We need it well
supported for TTS based AT, but also in other use cases. In particular I
believe we want to make sure this makes it into W3C specs such as Input


I believe we have two distinct use cases for Input Events:

1.)	All I/O switches to the new lang, TTS, on screen, and most
importantly keyboard. This is the easy, expected use case, imo.

2.)	For students just learning a language, however, I believe  we
probably want the on screen text, it's TTS, and inline lang keyboard,
but any feedback on attributes such as bold, italic, etc in the primary
language, not the temporary new inline language. After all, students are
learning and shouldn't be expected to have mastered the inline lang
sufficiently to understand everything they need to know about their
input in the inline lang just yet.

Phill Jenkins writes:
> and I would recommend that you still "chase-up Apple" so they hear the 
> feedback and address the need. 
> I recommend the same for IBM because it is when the teams hear over and 
> over the need for something that it gets prioritized higher. 
> ___________
> Regards,
> Phill Jenkins
> pjenkins@us.ibm.com
> From:   Michiel Bijl <michiel.list@moiety.me>
> To:     Corey Collins <ccollins@usc.edu.au>
> Cc:     "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
> Date:   11/15/2017 07:16 AM
> Subject:        Re: VoiceOver lang="" compatibility
> As far as I?m aware macOS doesn?t have support for automatic language 
> switching in VoiceOver. iOS does however. 
> ? Michiel
> On 15 Nov 2017, at 05:54, Corey Collins <ccollins@usc.edu.au> wrote:
> Hi Everyone
> Before I chase-up Apple, has anyone else experienced a compatibility issue 
> with the lang=?? attribute for VoiceOver?
> Something like the following reads/pronounces correctly in JAWS and NVDA 
> but VoiceOver tries to read the Spanish marked-up version phonetically as 
> English:
> <p>Translate es un servicio gratuito de traducción automática 
> multilingüe</p>
> <p><span lang="es">Translate es un servicio gratuito de traducción 
> automática multilingüe</span></p>
> Is this a known bug? I thought it may have been discussed before on the 
> mailing list but couldn?t find anything with a search.
> I also tested VoiceOver with the Webaim Document Language example with no 
> success.
> Thanks
> Corey Collins
> Web Accessibility Specialist
> Student Services and Engagement
> Ph +61 7 5456 5383?
> ccollins@usc.edu.au?
> usc.edu.au
> <image001.jpg>
> University of the Sunshine Coast?CRICOS Provider No. 01595D
> <image002.png>
> USC, Locked Bag 4, Maroochydore DC, Queensland, 4558 Australia.
> CRICOS Provider No: 01595D
> Please consider the environment before printing this email.
> This email is confidential. If received in error, please delete it from 
> your system.


Janina Sajka,	Phone:	+1.443.300.2200
		Email:	janina@rednote.net

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa
Received on Thursday, 16 November 2017 15:34:30 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 6 December 2017 16:04:47 UTC