Re: Comment / question re. Requirements for WCAG 2.0 Extensions

Thanks Andrew for  your response.
About Comment#2 below:
That example reads:
•Existing success criterion may be modified, but the resulting change
must still satisfy WCAG 2.0 success criteria
Question 1: modified in what way? It will help if the example expands
on the statement in the preceding para , "but extensions may not
weaken what is required of web content. ".
Question 2: "  satisfy WCAG 2.0 success criteria: Is the reference to
criteria deliberate or it is  meant to be criterion (singular)?
Maybe for example,  a particular SC today does not address the needs
of a particular PWD group and that may be added on by altering the
particular SC's wording.
So the scope of the change is one particular SC. ... Not success
criteria as I understand it because the example refers to "Existing
success criterion".

About Comment 3:
It may help if the statement in 2.5, "When a page conforms to an
extension at a specific level, that page must conform to WCAG 2.0 at
the same level" is  appended to the text in 2.4
Perhaps the intent stated in your email  should be more clear in the
requirements doc?
The hypothetical example  will be more helpful in section 2.4. I am in
favor of merging 2.4 and 2.5 really.
Thanks,
Sailesh


On 2/4/16, Andrew Kirkpatrick <akirkpat@adobe.com> wrote:
> Sailesh,
>
>
> Some comments within:
>
>>Ref: https://www.w3.org/TR/wcag2-ext-req/
>>
>>Comment 1. relating to Section 2.2
>>
>>Reference: "The result of this is that when a page conforms to WCAG
>>2.0 with an extension, it must also conform to WCAG 2.0 if the
>>extension is not considered in the conformance review".
>>Consider if this makes it more explicit and clearer:
>>The result of this is that a page that claims conformance to WCAG 2.0
>>plus an extension must also independently conform with all
>>requirements  of WCAG 2.0 at the stated level without considering the
>>extension.
>
> I like this change.  I think that it is entirely editorial in that it
> doesn’t change the meaning at all, but is clearer.  The “independently
> conform” phrase is helpful, I think.
>
>
>>Comment 2:   relating to Section 2.2 examples
>>I find this line a bit unclear:
>>Reference: "Existing success criterion may be modified, but the
>>resulting change must still satisfy WCAG 2.0 success criteria"
>>
>>Maybe it can be re-worded:
>>"An existing success criterion can be modified by the extension in a
>>manner that it adds additional conformance requirements without
>>diluting or decreasing what is already required by the success
>>criterion in WCAG 2.0.
>
> This change doesn’t quite hit it for me.  I think that the original is more
> clear.  What specifically isn’t clear in the original for you?
>
>
>>Comment 3: relating to Section 2.5:
>>Reference: "When a page conforms to an extension at a specific level,
>>that page must conform to WCAG 2.0 at the same level".
>>Question:
>>This will discourage a page author claiming conformance with Level A
>>WCAG 2.0 from  meeting  a particular extension  that covers  certain
>>Level AA  requirements. Maybe the page author does not choose to meet
>>all Level AA requirements except those covered  by this particular
>>extension.
>>So why can the author not say the page conforms with WCAG Level A +
>> Extension X?
>>This  will be more in line with what I understand from the statement
>>in Section 2.4:
>>"Extensions must specify that conformance claims indicate that a page
>>conforms to WCAG 2.0 as a base, and to the extension as an additional
>>layer of conformance."
>
> We discussed this in a few calls and considered this, but the group
> ultimately decided that conforming to WCAG 2.0 at the AA level was more
> important than conforming to the extension at AA if the page is only at A.
> It is possible for a page to be AA-conforming but only conform to the an
> extension at level A, but not the other way around.
>
> AWK
>
>

Received on Thursday, 4 February 2016 15:12:03 UTC