Re: simple language subtag

the w3c documents are all at   

www.w3.org/TR <http://www.w3.org/TR>

WCAG 2.0  is     https://www.w3.org/TR/WCAG20 <https://www.w3.org/TR/WCAG20>


WCAG 2.1   is     https://www.w3.org/TR/WCAG21/ <https://www.w3.org/TR/WCAG21/>



508 is on the Access Board  site:   AccessBoard.gov <http://accessboard.gov/>
look for ICT access guidelines  — a link to it is on the home page


Gregg C Vanderheiden
greggvan@umd.edu <mailto:greggvan@umd.edu>



> On Apr 27, 2017, at 3:05 PM, Kevin Meyers <kman2020@wi.rr.com <mailto:kman2020@wi.rr.com>> wrote:
> 
> Léonie, I don't have an answer on your question.  It is very unique you talk about WCAG20.  I have been looking at getting into this type of work.  I cannot find a class that teaches the 508 standards or W3C standards.  Plus I cannot find documents for either one.  I only find descriptions about these on the internet.  Where did you gain your knowledge?  Cheers, Kevin
> 
> Kevin Meyers
> I'm ready to rock, roll and race my tandem!
> http://www.mytruevision.net <http://www.mytruevision.net/>
> 
> -----Original Message-----
> From: Léonie Watson [mailto:tink@tink.uk] 
> Sent: Wednesday, April 26, 2017 9:14 PM
> To: Tobias Bengfort; w3c-wai-ig@w3.org
> Subject: Re: simple language subtag
> 
> 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.
> 
> 
> Léonie
> -- 
> @LeonieWatson tink.uk Carpe diem
> 
>> 
>> [1]: http://permalink.gmane.org/gmane.ietf.languages/11065
>> 
> 
>