- From: Jeffrey Singleton <j.singleton@hisoftware.com>
- Date: Sun, 21 Oct 2012 00:50:34 -0400
- To: "public-wai-evaltf@w3.org" <public-wai-evaltf@w3.org>
- CC: Ken Nakata <k.nakata@hisoftware.com>
- Message-ID: <7DF08B744286EA4FB231D3387AE43A845A2AB98865@VMBX112.ihostexchange.net>
The examples cited for the definition for "Common Functionality" in the current draft are more representative "Key User Scenarios" or "Key Transaction Paths". Consider adding a definition for the scenarios or transaction paths and focusing the common functionality definition on functionality that is common to all or the majority of pages. Such as adding an item to the shopping cart, entering a search string, or accessing a global menu. Common Functionality [Review Note: We are searching for input on this definition. We previously used the terms key functionality and primary functionality in this definition, but are searching for a better term.] [...] functionality of a website<http://www.w3.org/TR/WCAG-EM/#website> including tasks that users of a website<http://www.w3.org/TR/WCAG-EM/#website> carry out to perform this functionality. Note: Examples of functionality include "selecting and purchasing a product from the shop area of the website", "filling and submitting the form provided on the website", and "registering for an account on the website". Jeff Singleton HiSoftware, Inc. One Tara Boulevard, Suite 104 Nashua, NH 03062 j.singleton@hisoftware.com<mailto:k.nakata@hisoftware.com> direct: (425) 336-3676 office: (603) 318-3145 Jeff Singleton HiSoftware, Inc. One Tara Boulevard, Suite 104 Nashua, NH 03062 j.singleton@hisoftware.com<mailto:k.nakata@hisoftware.com> direct: (425) 336-3676 office: (603) 318-3145
Received on Tuesday, 23 October 2012 18:11:02 UTC