W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2017

Re: Draft Spec (2.1)

From: John Foliot <john.foliot@deque.com>
Date: Fri, 14 Jul 2017 12:56:49 -0500
Message-ID: <CAKdCpxwg+jqf9N-Sm8YwUYQdB8MJFC9j=xv1B4VmWRbXxq6eeA@mail.gmail.com>
To: Andrew Kirkpatrick <akirkpat@adobe.com>
Cc: WCAG <w3c-wai-gl@w3.org>

At some point, they both point to "The Glossary", except different
"glossaries" seem to exist depending on which issue is in play. I
understand that this is due to branches, but I am asking for a stable trunk
that I can use...

Lisa was upset that I hadn't read the "Glossary Entry" for Contextual
Information because I was looking at the Draft spec, and not her (or rather
the issue 6) branch... and then I inadvertently brought up a "wrong"
glossary because I was looking at the draft text related to Issue 38... I
mean, we have multiple instances of almost identical but not quite
identical "glossary" entries... *I'm* struggling with the cognitive
overload that is introducing.


On Fri, Jul 14, 2017 at 11:46 AM, Andrew Kirkpatrick <akirkpat@adobe.com>

> As a follow on to Thursday's meeting, can we ensure that all relevant
> glossary additions are being added to the draft spec as well?
> I added all of the links to the Issue 6 definitions today.
> https://rawgit.com/w3c/wcag21/support-personalization_ISSUE-6/
> guidelines/#support-personalization
> For example we need to have the definition for * contextual information *(
> https://rawgit.com/w3c/wcag21/support-personalization_ISSUE-6/
> guidelines/terms/21/contextual-information.html
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fwcag21%2Fsupport-personalization_ISSUE-6%2Fguidelines%2Fterms%2F21%2Fcontextual-information.html&data=02%7C01%7C%7Cdf4efe28919d4213039308d4cad2b1e8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636356453668346443&sdata=KUrnVW3wMG%2BRmT0w2k7yRwaLTijnI9eLG6YwlZnW%2Fk0%3D&reserved=0>)
> added to the spec dated June 30/2017 (https://www.w3.org/TR/WCAG21/
> #glossary
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fwcag21%2Fundo_ISSUE-38%2Fguidelines%2F%23glossary&data=02%7C01%7C%7Cdf4efe28919d4213039308d4cad2b1e8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636356453668346443&sdata=SfJlbbmominzJybDepRerKRigPGZpCMnk7oF4HrTO9I%3D&reserved=0>
> )
> I’m not following this – https://www.w3.org/TR/WCAG21/#glossary
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fwcag21%2Fundo_ISSUE-38%2Fguidelines%2F%23glossary&data=02%7C01%7C%7Cdf4efe28919d4213039308d4cad2b1e8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636356453668346443&sdata=SfJlbbmominzJybDepRerKRigPGZpCMnk7oF4HrTO9I%3D&reserved=0> above
> is resolving to a different URI so I’m not sure what you are really asking,
> but if you do mean the June 30 TR spec then we won’t add the contextual
> information definition to the editor’s draft until an SC that uses the
> definition is accepted into the editor’s draft.
> (Am I the only one struggling with the fact that this:
> https://rawgit.com/w3c/wcag21/undo_ISSUE-38/guidelines/#glossary
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fwcag21%2Fundo_ISSUE-38%2Fguidelines%2F%23glossary&data=02%7C01%7C%7Cdf4efe28919d4213039308d4cad2b1e8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636356453668346443&sdata=SfJlbbmominzJybDepRerKRigPGZpCMnk7oF4HrTO9I%3D&reserved=0>
> ..and this:
> https://rawgit.com/w3c/wcag21/support-personalization_ISSUE-
> 6/guidelines/#glossary
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frawgit.com%2Fw3c%2Fwcag21%2Fsupport-personalization_ISSUE-6%2Fguidelines%2F%23glossary&data=02%7C01%7C%7Cdf4efe28919d4213039308d4cad2b1e8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636356453668346443&sdata=E5v%2FubZtY3qe%2BrdK2imARBkUsFpKoK3ggKMxVzydPH8%3D&reserved=0>
> are functionally different when it comes to definitions? {And / But the
> differences are hard to spot})
> I’m not clear on what differences you mean – Issue 38 has no definitions
> at this time, and Issue 6 does…

John Foliot
Principal Accessibility Strategist
Deque Systems Inc.

Advancing the mission of digital accessibility and inclusion
Received on Friday, 14 July 2017 17:57:17 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:15 UTC