Re: Diagram of WCAG Extension integration into WCAG (Proposal)

I concur, excellent diagram David!

One thought, though, I was wondering if the diagram may be too centric 
on the internal WG view rather than the user view. Specifically, the 
normative and non-normative parts are unconnected in the development 
process, but they are connected for the user - mainly through the "How 
to Meet WCAG 2.0" quick reference, which is currently being redesigned. 
I think this may also be a good resource for plugging-in the extensions 
into the WCAG 2 suite of documents seamlessly to the users of WCAG.

So, my suggestion - if acceptable to the group - is to add the "How to 
Meet WCAG 2.0" quick reference to the diagram, as the "interface" for 
the work that is produced in the depicted diagram. I think this would 
make the diagram more complete, but also to keep reminding ourselves 
about the integration and usability of the actual work outcomes.

Best,
   Shadi


On 27.9.2015 13:52, Laura Carlson wrote:
> Hi David,
>
> Thank you!
>
> The diagram s much clearer. I like it a lot.
>
> Kindest Regards,
> Laura
>
>
> On 9/26/15, David MacDonald <david100@sympatico.ca> wrote:
>> PS I added the "Digital Learning" box task force to the diagram.
>>
>> http://davidmacd.com/blog/WCAG-extension-proposed-integration-into-WCAG.html
>>
>>
>> Cheers,
>>
>> David MacDonald
>>
>>
>>
>> *Can**Adapt* *Solutions Inc.*
>>
>> Tel:  613.235.4902
>>
>> LinkedIn <http://www.linkedin.com/in/davidmacdonald100>
>>
>> www.Can-Adapt.com
>>
>>
>>
>> *  Adapting the web to all users*
>> *            Including those with disabilities*
>>
>> If you are not the intended recipient, please review our privacy policy
>> <http://www.davidmacd.com/disclaimer.html>
>>
>> On Fri, Sep 25, 2015 at 10:12 AM, David MacDonald <david100@sympatico.ca>
>> wrote:
>>
>>> Thanks Laura
>>>
>>> It looks good, has advantage of being simpler, and I really like the
>>> funnel. Perhaps the disadvantage of dividing them is that in practice,
>>> the
>>> non-normative and normative work are interrelated, a messy process of
>>> things emerging as success criteria and other being relegated to
>>> techniques
>>> tends to come out of the same work processes rather than separate work
>>> items. However, the important thing is that we are on the same page and
>>> understand the proposal... so they are both useful diagrams... thanks for
>>> jumping in...
>>>
>>> Cheers,
>>>
>>> David MacDonald
>>>
>>>
>>>
>>> *Can**Adapt* *Solutions Inc.*
>>>
>>> Tel:  613.235.4902
>>>
>>> LinkedIn <http://www.linkedin.com/in/davidmacdonald100>
>>>
>>> www.Can-Adapt.com
>>>
>>>
>>>
>>> *  Adapting the web to all users*
>>> *            Including those with disabilities*
>>>
>>> If you are not the intended recipient, please review our privacy policy
>>> <http://www.davidmacd.com/disclaimer.html>
>>>
>>> On Thu, Sep 24, 2015 at 6:13 PM, Laura Carlson <
>>> laura.lee.carlson@gmail.com> wrote:
>>>
>>>> Hi David,
>>>>
>>>> Yes. This is a big improvement. Thanks.
>>>>
>>>> The following is a take on simplfying it further by splitting it into
>>>> 2 flow charts.
>>>> http://www.d.umn.edu/~lcarlson/wcagwg/extensions/integration.html
>>>>
>>>> Kindest Regards,
>>>> Laura
>>>>
>>>> On 9/24/15, David MacDonald <david100@sympatico.ca> wrote:
>>>>> I've taken the feedback and created another diagram that may be
>>>>> clearer.
>>>>> I've tried to simplify it, particularly reducing the complexity of the
>>>>> errors.
>>>>>
>>>>>
>>>> http://davidmacd.com/blog/WCAG-extension-proposed-integration-into-WCAG.html
>>>>>
>>>>> Cheers,
>>>>>
>>>>> David MacDonald
>>>>>
>>>>>
>>>>>
>>>>> *Can**Adapt* *Solutions Inc.*
>>>>>
>>>>> Tel:  613.235.4902
>>>>>
>>>>> LinkedIn <http://www.linkedin.com/in/davidmacdonald100>
>>>>>
>>>>> www.Can-Adapt.com
>>>>>
>>>>>
>>>>>
>>>>> *  Adapting the web to all users*
>>>>> *            Including those with disabilities*
>>>>>
>>>>> If you are not the intended recipient, please review our privacy
>>>>> policy
>>>>> <http://www.davidmacd.com/disclaimer.html>
>>>>>
>>>>> On Thu, Sep 24, 2015 at 12:38 PM, David MacDonald <
>>>> david100@sympatico.ca>
>>>>> wrote:
>>>>>
>>>>>> Hi Detlev
>>>>>>
>>>>>>>> "WCAG Extension" is both the label of the blob in the normative
>>>> section
>>>>>> BUT ALSO heads the WCAG extensions to the left (the boxes Mobile,
>>>>>> Coginitve, Low vision).
>>>>>>
>>>>>> The proposal is that the left side is the the individual task force
>>>> work.
>>>>>> Any success criteria and guidelines would be gathered up and adjusted
>>>> for
>>>>>> redundancies etc,
>>>>>>
>>>>>>>> The meaning of the arrows could be that some or all of that stuff
>>>> feeds
>>>>>> into a normative extension or that there a relation of sorts between
>>>> two
>>>>>> separate things.
>>>>>>
>>>>>> Yes, I'm suggesting that the three extensions could be combined into
>>>> one
>>>>>> normative extension.
>>>>>>
>>>>>>>>> it doesn't tell me clearly if and when I need to meet the
>>>>>>>>> Extension
>>>> to
>>>>>> claim WCAG 2.0 conformance.
>>>>>>
>>>>>> WCAG 2 will never change, so the extension circle is not required to
>>>> meet
>>>>>> WCAG 2 but if some jurisdiction requires "WCAG2 + Extension", then it
>>>>>> would
>>>>>> be required in addition to WCAG. That is why it is in the normative
>>>>>> box...
>>>>>> Normative means it will go through a formal acceptance procedure
>>>>>> which
>>>> is
>>>>>> very rigorous. Once something is declared normative it is very hard
>>>>>> to
>>>>>> change... that would be any Guidelines and Success Criteria that the
>>>> task
>>>>>> forces make, and are approved.
>>>>>>
>>>>>> Explanation of Normative https://en.wikipedia.org/wiki/Normative
>>>>>>
>>>>>> The techniques we work up in the task forces will go into the
>>>>>> "informative" bucket... they are non normative and can be easily
>>>> changed,
>>>>>> fixed, or adapted and they can be referenced either by the extension
>>>>>> or
>>>>>> the
>>>>>> core WCAG.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> David MacDonald
>>>>>>
>>>>>>
>>>>>>
>>>>>> *Can**Adapt* *Solutions Inc.*
>>>>>>
>>>>>> Tel:  613.235.4902
>>>>>>
>>>>>> LinkedIn <http://www.linkedin.com/in/davidmacdonald100>
>>>>>>
>>>>>> www.Can-Adapt.com
>>>>>>
>>>>>>
>>>>>>
>>>>>> *  Adapting the web to all users*
>>>>>> *            Including those with disabilities*
>>>>>>
>>>>>> If you are not the intended recipient, please review our privacy
>>>>>> policy
>>>>>> <http://www.davidmacd.com/disclaimer.html>
>>>>>>
>>>>>> On Thu, Sep 24, 2015 at 11:00 AM, Detlev Fischer <
>>>>>> detlev.fischer@testkreis.de> wrote:
>>>>>>
>>>>>>> What I currently find confusing is that "WCAG Extension" is both the
>>>>>>> label of the blob in the normative section BUT ALSO heads the WCAG
>>>>>>> extensions to the left (the boxes Mobile, Coginitve, Low vision).
>>>>>>> The
>>>>>>> meaning of the arrows could be that some or all of that stuff feeds
>>>> into
>>>>>>> a
>>>>>>> normative extension or that there a relation of sorts between two
>>>>>>> separate
>>>>>>> things.  The diagram also leaves me uncertain as to the exact status
>>>> of
>>>>>>> *the* Extension or the *extensions* - it doesn't tell me clearly if
>>>> and
>>>>>>> when I need to meet the Extension to claim WCAG 2.0 conformance.
>>>>>>>
>>>>>>> --
>>>>>>> Detlev Fischer
>>>>>>> testkreis c/o feld.wald.wiese
>>>>>>> Thedestr. 2, 22767 Hamburg
>>>>>>>
>>>>>>> Mobil +49 (0)1577 170 73 84
>>>>>>> Tel +49 (0)40 439 10 68-3
>>>>>>> Fax +49 (0)40 439 10 68-5
>>>>>>>
>>>>>>> http://www.testkreis.de
>>>>>>> Beratung, Tests und Schulungen für barrierefreie Websites
>>>>>>>
>>>>>>> Laura Carlson schrieb am 24.09.2015 16:33:
>>>>>>>
>>>>>>>> Hi David and all,
>>>>>>>>
>>>>>>>> I think the idea of a  flowchart to depicted how separate
>>>>>>>> extensions
>>>>>>>> become 1 unified WCAG extension is great. Reminds me of those "How
>>>>>>>> a
>>>>>>>> bill becomes a law" diagrams.
>>>>>>>>
>>>>>>>> I gave the flowchart it's own section on the WCAG 2 Extension
>>>>>>>> Principles Wiki Page.
>>>>>>>> https://www.w3.org/WAI/GL/wiki/WCAG_2_Extension_Principles
>>>>>>>>
>>>>>>>> Thanks for your hard work.
>>>>>>>>
>>>>>>>> Best regards,
>>>>>>>> Laura
>>>>>>>>
>>>>>>>> On 9/24/15, Srinivasu Chakravarthula <
>>>>>>> srinivasu.chakravarthula@deque.com>
>>>>>>>> wrote:
>>>>>>>>> +1 Great work, David.
>>>>>>>>>
>>>>>>>>> >From the beginning at least my understanding is that TFs are
>>>>>>> subgroups of
>>>>>>>>> WGs.
>>>>>>>>> Best,
>>>>>>>>> Srini
>>>>>>>>>
>>>>>>>>> Best regards,
>>>>>>>>>
>>>>>>>>> *Srinivasu Chakravarthula*
>>>>>>>>> Sr. Accessibility Consultant, *Deque* <http://deque.com>
>>>>>>>>> Hand phone: +91 709 380 3855
>>>>>>>>>
>>>>>>>>> Deque University <http://dequeuniversity.com> | Follow me on
>>>> Twitter
>>>>>>>>> <http://twitter.com/CSrinivasu> | Connect on LinkedIn
>>>>>>>>> <http://linkedin.com/in/srinivasuc> | About Me <
>>>>>>> http://about.me/srinivasuc>
>>>>>>>>>
>>>>>>>>> Technology is a gift to everyone; let's create inclusive digital
>>>>>>> experience
>>>>>>>>>
>>>>>>>>> On Thu, Sep 24, 2015 at 2:05 PM, josh@interaccess.ie <
>>>>>>> josh@interaccess.ie>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>>> Great stuff David! As discussed on the call yesterday - one area
>>>>>>>>>> that
>>>>>>>>>> your diagram would need to address is the nexus/delta between
>>>>>>>>>> related
>>>>>>>>>> techniques (as outputs from various TFs that cover users in
>>>>>>>>>> other
>>>>>>>>>> groups).
>>>>>>>>>>
>>>>>>>>>> At least to indicate that in your document flow would be good as
>>>> the
>>>>>>>>>> techniques may not always be exclusively related to the needs of
>>>>>>>>>> each
>>>>>>> TFs
>>>>>>>>>> target user group.
>>>>>>>>>>
>>>>>>>>>> I also think that the Mobile TF, Cognitive TF  and Low Vision TF
>>>>>>>>>> work
>>>>>>>>>> belongs 'inside' the 'WCAG Extension' Circle, as the TFs are
>>>> tasked
>>>>>>> to do
>>>>>>>>>> this work, and your visual representation indicates that they
>>>>>>>>>> may
>>>> be
>>>>>>>>>> separate.
>>>>>>>>>>
>>>>>>>>>> Good work though :-)
>>>>>>>>>>
>>>>>>>>>> Josh
>>>>>>>>>>
>>>>>>>>>> ------ Original Message ------
>>>>>>>>>> From: "David MacDonald" <david100@sympatico.ca>
>>>>>>>>>> To: "WCAG" <w3c-wai-gl@w3.org>
>>>>>>>>>> Sent: 23/09/2015 21:14:56
>>>>>>>>>> Subject: Diagram of WCAG Extension integration into WCAG
>>>> (Proposal)
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> I've created a diagram of how we might integrate the extensions
>>>> into
>>>>>>>>>> a
>>>>>>>>>> single document.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>
>>>> http://davidmacd.com/blog/WCAG-extension-proposed-integration-into-WCAG.html
>>>>>>>>>>
>>>>>>>>>> Description:
>>>>>>>>>> The task forces, Mobile, Cognitive, and Low Vision would develop
>>>>>>>>>> guidelines, success criteria and techniques separately, and then
>>>>>>>>>> integrate
>>>>>>>>>> them to resolve conflicts and overlaps and then integrate them
>>>> into
>>>>>>> the
>>>>>>>>>> singular WCAG extension. The techniques would be collected in a
>>>> non
>>>>>>>>>> normative document as techniques for the extension, and some of
>>>> them
>>>>>>> can
>>>>>>>>>> be
>>>>>>>>>> referenced from WCAG 2 where the techniques might apply to an
>>>>>>>>>> existing
>>>>>>>>>> Success criteria.
>>>>>>>>>>
>>>>>>>>>> Cheers,
>>>>>>>>>>
>>>>>>>>>> David MacDonald
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *Can**Adapt* *Solutions Inc.*
>>>>>>>>>>
>>>>>>>>>> Tel:  613.235.4902
>>>>>>>>>>
>>>>>>>>>> LinkedIn <http://www.linkedin.com/in/davidmacdonald100>
>>>>>>>>>>
>>>>>>>>>> www.Can-Adapt.com <http://www.can-adapt.com/>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> *  Adapting the web to all users*
>>>>>>>>>> *            Including those with disabilities*
>>>>>>>>>>
>>>>>>>>>> If you are not the intended recipient, please review our privacy
>>>>>>> policy
>>>>>>>>>> <http://www.davidmacd.com/disclaimer.html>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Laura L. Carlson
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Laura L. Carlson
>>>>
>>>>
>>>>
>>>
>>
>
>

-- 
Shadi Abou-Zahra - http://www.w3.org/People/shadi/
Activity Lead, WAI International Program Office
W3C Web Accessibility Initiative (WAI)

Received on Monday, 28 September 2015 06:27:47 UTC