- From: Kirill Gavrylyuk <kirillg@microsoft.com>
- Date: Fri, 18 Jan 2002 08:41:41 -0800
- To: "Lofton Henderson" <lofton@rockynet.com>
- Cc: <www-qa-wg@w3.org>
- Message-ID: <B3F0DACD72892E4DB7E8296C6C9FC2F60414C065@red-msg-03.redmond.corp.microsoft.com>
I don't see any confusion here - we decided to change to imperative voice and priorities. Pure cosmetic issue. Thanks -----Original Message----- From: Lofton Henderson [mailto:lofton@rockynet.com] Sent: Thursday, January 17, 2002 1:09 PM To: Kirill Gavrylyuk Cc: www-qa-wg@w3.org Subject: must/should/may Clearly, I was confused on this one. Ian's mail said, "* use the WAI style of the imperative voice for guidelines and checkpoints." (I remembered about guidelines but not checkpoints.) Daniel's message ([1]) said essentially the same (or alternately, use priorities or normative keywords, not both). Sorry if I created confusion here! -Lofton. [1] http://lists.w3.org/Archives/Public/www-qa/2002Jan/0011.html Excerpt from WCAG Checklist... Priorities Each checkpoint has a priority level assigned by the Working Group based on the checkpoint's impact on accessibility. [Priority 1] A Web content developer must satisfy this checkpoint. Otherwise, one or more groups will find it impossible to access information in the document. Satisfying this checkpoint is a basic requirement for some groups to be able to use Web documents. [Priority 2] A Web content developer should satisfy this checkpoint. Otherwise, one or more groups will find it difficult to access information in the document. Satisfying this checkpoint will remove significant barriers to accessing Web documents. [Priority 3] A Web content developer may address this checkpoint. Otherwise, one or more groups will find it somewhat difficult to access information in the document. Satisfying this checkpoint will improve access to Web documents.
Received on Friday, 18 January 2002 11:42:14 UTC