W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2016

Re: Discussion on SC numbering

From: David MacDonald <david100@sympatico.ca>
Date: Mon, 19 Dec 2016 14:38:27 -0500
Message-ID: <CAAdDpDaqXtoZyvHFGRrSTRjfLHLjVHFpbF=fH-DpvKGg2QjTkQ@mail.gmail.com>
To: "White, Jason J" <jjwhite@ets.org>
Cc: Andrew Kirkpatrick <akirkpat@adobe.com>, WCAG <w3c-wai-gl@w3.org>
 >I think that getting the language right is hard enough and that if we are
trying to write it as integrated but then publish it as separate SCs we
will run into additional challenges.

Perhaps I don't understand, I was thinking for instance in WCAG 2.0 SC
1.4.4, says:

*            1.4.4
<http://www.w3.org/TR/2008/REC-WCAG20-20081211/#visual-audio-contrast-scale>
Resize
text:* Except for captions
<https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-scale.html#captionsdef>
 and images of text
<https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-scale.html#images-of-textdef>
, text
<https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-scale.html#textdef>
can
be resized without assistive technology
<https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-scale.html#atdef>
up
to 200 percent without loss of content or functionality. (Level AA)

In 2.1 It might say something like this:

1.4.4 The content of the Web page can be increased to 400% without loss of
content or functionality, without two dimensional scrolling, with following
the exceptions:

   1. If the spatial layout of some the content is essential to that
   contents use, that part of the content is exempt.
   2. If the user-agent fits the layout to the viewport and does not
   provide a means of reflowing content, two dimensional scrolling is exempt.



On Mon, Dec 19, 2016 at 1:42 PM, White, Jason J <jjwhite@ets.org> wrote:

>
>
>
>
> *From:* David MacDonald [mailto:david100@sympatico.ca]
>
> I think for cases where we are modifying an existing SC, we track it as
> changes are being made but on the final, just release the new SC language.
> For reference we can also release a supporting document that shows the
> changes.
>
> *[Jason] Or list them in an appendix. I think usability of the document is
> of paramount concern, and that having a clean document which avoids
> comparing old with new in the normative sections does much to enhance
> usability.*
>
>
>
> ------------------------------
>
> This e-mail and any files transmitted with it may contain privileged or
> confidential information. It is solely for use by the individual for whom
> it is intended, even if addressed incorrectly. If you received this e-mail
> in error, please notify the sender; do not disclose, copy, distribute, or
> take any action in reliance on the contents of this information; and delete
> it from your system. Any other use of this e-mail is prohibited.
>
> Thank you for your compliance.
> ------------------------------
>
Received on Monday, 19 December 2016 19:39:01 UTC

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