- From: Jan Richards <jan.richards@utoronto.ca>
- Date: Fri, 09 Jun 2006 15:33:00 -0400
- To: WAI-AUWG List <w3c-wai-au@w3.org>
B.3.3 looks good - it was fixed up earlier in this process. I just wonder about the wording "classes of Web content problems". Maybe it should be "types of Web content problems". B.2.5 looks good. A.1.3 looks good - should point to definition of Platform in: http://lists.w3.org/Archives/Public/w3c-wai-au/2006AprJun/0068.html (if this is adopted) A.2.6 looks good - just change "browsers" to "user agents" B.2.7 (was B.2.9): looks good A.3.2: SC1 changes in CAPS; Fold SC2 into SC1; SC3 changes in CAPS SC1: User interface controls THAT ARE IDENTIFIED BY the same text label or icon must ALWAYS perform the same function. new SC2: When the same function (e.g. saving, INVOKING a checker, canceling an action) is available in multiple areas of THE user interface, at least one method of OPERATING the function in each area MUST USE identical user interface CONTROLS (e.g. the same text labels, icons, button appearances). A.2.5 looks good - except... SC1: "to any other element with ANY OF the following relationshipS" SC2: "When editing content that is a structured element set, the author must be able to select ANY ELEMENT and perform editing functions (e.g. cut, copy, paste, presentation) on THAT ELEMENT, ITS CONTENT AND ITS sub-elements. B.3.6 (was B.2.8): CP text: "authoring practices" => "authoring actions" Rationale: ..."This can also facilitate a better understanding of the reasoning behind accessible content AND THE CONSEQUENCES OF ACCESSIBILITY PROBLEMS. B.3.2 - looks good B.3.4 - looks good - except for rationale with outdated reference to configurability, a term that should prob be removed (http://lists.w3.org/Archives/Public/w3c-wai-au/2006AprJun/0058) Rationale: The accessible content support features will be more adaptable to the work habits of more authors if they can be turned on and off easily as the author needs them.
Received on Friday, 9 June 2006 19:37:07 UTC