W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > September 2011

Re: Use of "should" and "must" defined

From: Loretta Guarino Reid <lorettaguarino@google.com>
Date: Mon, 26 Sep 2011 17:21:49 -0700
Message-ID: <CAHu5OWbhiyybtpxUwcLq0VickX_9rKFAGVqNNEj4xcY+TEsJCQ@mail.gmail.com>
To: glenda.sims@deque.com
Cc: public-comments-wcag20@w3.org
On Tue, Apr 19, 2011 at 12:31 PM, <noreply@w3.org> wrote:

> Name: Glenda Sims
> Email: glenda.sims@deque.com
> Affiliation: Senior Accessibility Consultant at Deque
> Document: TD
> Item Number: G141
> Part of Item: Description
> Comment Type: editorial
> Summary of Issue: Use of "should" and "must" defined
> Comment (Including rationale for any proposed change):
> It might be useful to clearly indicate the definition of the words "should"
> and "must" for the purpose of requirements versus recommendations.  This
> would apply to all parts of WCAG 2.0.  I mentioning it here on this
> technique, because this is where I recently had a debate about what "should"
> means versus what "must" means.
> Proposed Change:
> Make it obvious that "should" is recommended while "must" is required.  You
> could use the definitions found at http://www.ietf.org/rfc/rfc2119.txt.
>  You could also consider making the words "must" and "should" hotlink to the
> definition.  Or, not.  Just an idea.
> ================================
Response from the Working Group
We are adding the following discussion of the uses of "must" and "should" in
techniques to the introduction to the Techniques document. We hope that this
will clarify interpretations of the techniques.


We are not using RFC 2119 in our standard because it cannot be applied in a
standard like ours with 3 levels of conformance.

Please let us know whether this still leaves misinterpretations in our uses
of these terms.

Loretta Guarino Reid, WCAG WG Co-Chair
Gregg Vanderheiden, WCAG WG Co-Chair
Michael Cooper, WCAG WG Staff Contact

On behalf of the WCAG Working Group
Received on Tuesday, 27 September 2011 00:22:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:14:55 UTC