Re: Converting JSON from 2.0 to 2.1

Hi Stéphane,

On 10 Oct 2018, at 17:39, stephane.deschamps@orange.com wrote:

> Hi WG,
>
> Quick question, sorry if it's silly:
>
> I'm updating the JSON that Karl Groves shared on github[1] from 
> WCAG2.0 to 2.1, and I found that URLs were moved around.

There is a semi-official WCAG 2.1 JSON file in the quickref repository:

https://github.com/w3c/wai-wcag-quickref/blob/gh-pages/_data/wcag21.json

> Can I safely assumed that all URLs from schema 1 were migrated to 
> schema 2 below? Or must I check manually?
>
> How to meet:
> 1. http://www.w3.org/WAI/WCAG20/quickref/*
> 2. https://www.w3.org/WAI/WCAG21/quickref/*

Here, it is preferred to use the new WCAG 2.1 anchors now.

>
> Understanding guidelines:
> 1. http://www.w3.org/TR/UNDERSTANDING-WCAG20/*
> 2. https://www.w3.org/WAI/WCAG21/Understanding/*

For the understanding, it is also the new anchor names used for the 
files:

https://www.w3.org/TR/UNDERSTANDING-WCAG20/media-equiv-av-only-alt.html 
-> https://www.w3.org/WAI/WCAG21/Understanding/text-alternatives

The techniques are now in a directory according to their type, so 
H123.html is now in /html/h123.html

> WCAG themselves:
> 1. https://www.w3.org/TR/WCAG20/*
> 2. https://www.w3.org/TR/WCAG21/*

All the anchors in the page have changed as well. I have been able to 
preserve them in the quickref but they need to be changed for all SCs.

>
> Thanks in advance!
>
> [1] https://github.com/karlgroves/wcag-as-json

To be honest, I guess it is easier to use the quickref-json and form 
another json from it than (manually) changing links.

Hope that helps,
Eric

>
> -- 
> Cordialement / Kind regards
> Stéphane Deschamps
> Référent accessibilité - Direction Digitale - Expérience et 
> Interface Utilisateur
> Orange/OF/DMGP/DD/EIU
> mobile +33 6 37 30 65 31 (preferably text please)
> stephane.deschamps@orange.com
>
>
> _________________________________________________________________________________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations 
> confidentielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez 
> recu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les 
> messages electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, 
> deforme ou falsifie. Merci.
>
> This message and its attachments may contain confidential or 
> privileged information that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and 
> delete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have 
> been modified, changed or falsified.
> Thank you.



--

Eric Eggert
Web Accessibility Specialist
Web Accessibility Initiative (WAI) at World Wide Web Consortium (W3C)

Received on Wednesday, 10 October 2018 16:26:38 UTC