Re: Priorities

> Technique 1.1.K is priority 3.  However, it is a technique of a Priority 1
> checkpoint.
>
This is a mistake in the ERT. Requiring a text description for ASCII art is
priority 1. 'Provide a means to skip over multi-line ASCII art' is priority
3. So technique 1.1.K should be priority 1.

> If the priority of the WCAG checkpoint is not inherited, then how do we
> define priorities for this document?
>
The techniques should inherit the priority of the WCAG checkpoint.

> If we are expecting people to conform to it, then I think that implies we
> want to take this to Recommendation status.  Do we want to take it to
> Recommendation or release it as a Note?
>
What are the politics involved in taking it to a Recommendation? Would it
slow us down?

Chris



----- Original Message -----
From: Wendy A Chisholm <wendy@w3.org>
To: <w3c-wai-er-ig@w3.org>
Sent: Sunday, January 23, 2000 5:27 PM
Subject: Priorities


> Technique 1.1.K is priority 3.  However, it is a technique of a Priority 1
> checkpoint.
>
> If the priority of the WCAG checkpoint is not inherited, then how do we
> define priorities for this document? I do not believe we can inherit the
> priority definitions from WCAG.  The priority definitions would probably
be
> similar to ATAG [1] yet have to be stated in the context of this document.
>
> If we define priorities for this document, are we expecting people to
> conform to it?
>
> If we are expecting people to conform to it, then I think that implies we
> want to take this to Recommendation status.  Do we want to take it to
> Recommendation or release it as a Note?
>
> thoughts?
> --wendy
>
> [1] http://www.w3.org/TR/1999/PR-WAI-AUTOOLS-19991026/#priorities
> --
> wendy a chisholm
> world wide web consortium
> web accessibility initiative
> madison, wi usa
> tel: +1 608 663 6346
> /--

Received on Tuesday, 25 January 2000 09:49:27 UTC