- From: Jan Richards <jan.richards@utoronto.ca>
- Date: Mon, 11 Jul 2005 14:24:42 -0400
- To: "List (WAI-AUWG)" <w3c-wai-au@w3.org>
A.?.1 Ensure that browser-accessed functionality conforms to WCAG [Priority RP]. PROPOSED: Rationale: Authors must be able to have access to authoring tool functionality that is implemented as Web content. Note: For non-Web-based authoring tools, this is a relatively straightforward requirement, likely covering only a few areas of the interface (i.e. Web-based help features, etc.). However, for most Web-based authoring tools the requirement will cover the majority of functionality in the tool and overlap most of the other requirements in Part A of the guidelines. Techniques: ??? Success Criteria: 1. Any component of an authoring tool that is accessed by the author within a Web browser must conform to WCAG. --- CURRENT Rationale: ???.@@JR@@ Note: ???.@@applies to the authoring tool user interface and the editing views@@ - @@a drawback is that it imposes a higher/different requirement than for non-Web based tools@@ Techniques: ??? Success Criteria: 1. Any component of an authoring tool that is accessed by the author within a Web browser must conform to WCAG. --- Cheers, Jan
Received on Monday, 11 July 2005 18:25:18 UTC