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

Re: simple language subtag

From: Tobias Bengfort <tobias.bengfort@posteo.de>
Date: Thu, 27 Apr 2017 07:44:19 +0200
To: tink@tink.uk, w3c-wai-ig@w3.org
Message-ID: <0a2941ed-42a3-614f-dbb6-a6597c8120ed@posteo.de>
On 27/04/17 04:13, LĂ©onie Watson wrote:
> On 21/04/2017 18:42, Tobias Bengfort wrote:
>> back in september 2015 I sent a message to this list asking about
>> opinions on a "simple" language variant subtag. This would allow to
>> provide a "version that does not require reading ability more advanced
>> than the lower secondary education level" (WCAG20 3.1.5) like this:
>>   <link href="..." hreflang="en-simple" rel="alternate" />
>> In the meantime, this variant subtag has actually been registered[1]
>> (not by me).
>> Should the technique described above be included in the "How to Meet
>> WCAG 2.0" document? Or should we wait for ATs to actually support this?
>> If so, how can we push support in ATs?
> Can you suggest which AT should be able to utilise this information and
> in what way? As a piece of metadata that search engines could use to
> return results with simplified content, I think there is a good use
> case, but I'm not sure what screen reader, screen magnifier, or speech
> recognition support might look like.

My idea was that my user agent could help me find the simple language
version. It could either switch to it automatically or ask me every
time. In my head this looks a lot like the automatic translation feature
in chrome[1].

This could be implemented either as an option in mainstream browsers or
as a browser extension. Maybe the term AT is not a perfect fit.

Of course, there could be other technologies that I have not yet thought of.


[1]: https://www.youtube.com/watch?v=HqmUbNGkM9I
Received on Thursday, 27 April 2017 05:45:31 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 27 April 2017 05:45:34 UTC