- From: John Foliot <john@foliot.ca>
- Date: Thu, 18 Feb 2021 11:17:14 -0500
- To: Léonie Watson <lwatson@tetralogical.com>
- Cc: WCAG <w3c-wai-gl@w3.org>
- Message-ID: <CAKdCpxy4xmydpei0mk74-vEL9HfCrShQTYxfrgzCKPsdc19PRQ@mail.gmail.com>
Hi Léonie, You are mostly correct in your recollection in that there is a desire for a registry to store bits and bobs that are related to W3C specs, but should perhaps not be included I normative specs (too brittle), yet also not be left to a free-for-all (microformats taxonomies in a public wiki). The stop-gap solution for Success Criteria 1.3.5 was to include those fixed terms (taxonomy) directly in WCAG 2.1 (as Section 7). I suspect that as we advance the Personalization work <https://www.w3.org/TR/personalization-semantics-1.0/> (more fixed taxonomies) that the need for such a W3C registry will surface once again. To my mind, what we need is something as formal as /TR/, but with the ability for working groups to make changes to this type of content via a formal process slightly less onerous than a full spec update. Make sense? I'd voice a huge +1 for any advancement in that direction. HTH JF On Thu, Feb 18, 2021 at 10:10 AM Léonie Watson <lwatson@tetralogical.com> wrote: > Hello AG, > > I recall that there has been discussion about the use of registries with > WCAG. If my memory is correct it was John Folio that first mentioned it, > possibly in relation to storing things like the autocomplete values for > 1.3.5 (Identify Input Purpose), but I may be wrong about the detail. > > I'm mentioning it now because the W3 Process CG has been trying to > figure out registries and could use some input from WG that might find > them useful. > > The issue is here: > https://github.com/w3c/w3process/issues/168 > > Léonie. > > > -- > Director @TetraLogical > https://tetralogical.com/ > >
Received on Thursday, 18 February 2021 16:18:05 UTC