- From: Jan Richards <jan.richards@utoronto.ca>
- Date: Wed, 31 May 2006 16:51:44 -0400
- To: WAI-AUWG List <w3c-wai-au@w3.org>
Checkpoint text: Reword from: A.2.9 For the authoring tool user interface, ensure previews emulate the accessible rendering features of target user agents. [Priority 2] to: A.2.9 For the authoring tool user interface, ensure previews are at least as accessible as browsers. [Priority 2] Rationale: OK Rationale: Preview features are provided in many authoring tools because the workflow of authors often includes periodically checking how content will appear to end users in a user agent. In order to enable authors with disabilities to follow the same workflow as other authors, they must have access to any preview features that exist. Notes: Minor changes to Note 2. Note 1: Authors, including those with disabilities, will not be well-served if preview features diverge too much from the actual functionality of available user agents. Therefore, preview features are exempted from necessarily having to meet all of the other requirements in Part A of this guidelines document, if they meet this checkpoint. Note 2: It is understood that the accessibility of the content display of a preview will be negatively affected if the content being rendered is inaccessible or incomplete. For example, if markup tags are missing, a PREVIEWING USER AGENT may not render IT properly. Success Criteria: Minor rewording to SC2 1. If a preview feature is provided, then a method of returning from the preview must be provided that meets all of the checkpoints in Part A. 2. If a preview FEATURE is provided, then it must meet at least one of the following: (a) the preview makes use of an existing user agent (e.g. a third-party browser or browser control), or (b) the preview meets all of the checkpoints in Part A. TECHNIQUES: a few minor changes in CAPS Techniques for SC1): Applicability: This success criteria is applicable to authoring tools that have a preview function. Technique A.2.9-1.1 [Sufficient]: Launching the preview in a new window that the author can close in a conventional fashion. Technique A.2.9-1.2 [Sufficient]: Running the preview within the authoring tool user interface such that the author can easily escape from or stop the preview regardless of the state of the preview. Techniques for Success Criteria 2 (If a preview is provided, then it must meet at least one of the following: (a) the preview makes use of an existing user agent (e.g. a third-party browser or browser control), or (b) the preview meets all of the checkpoints in Part A.): Applicability: This success criteria is not applicable to authoring tools that lack a preview function. Technique A.2.9-2.1 [Sufficient for (a)]: Allowing the author to locate a browser on the platform with which to perform the preview). Technique A.2.9-2.2 [Sufficient for (a)]: For Web-based authoring tools, that are already running in a browser, use that browser to perform be the preview. Technique A.2.9-2.3 [Advisory for (a)]: Allowing the author to save a list of user agents to save time. Technique A.2.9-2.4 [Advisory for (a)]: Helping the author to find a user agent to perform the preview, by auto-scanning the system for known user agents. Technique A.2.9-2.5 [Advisory for (a)]: Bundling user agent installer files or providing a list of download sites for appropriate user agents. Technique A.2.9-2.6 [Sufficient for (b)]: Ensuring that the preview (content view and the rest of the user interface) meets all of the requirements of Part A that might apply to a browser (i.e. not A.2.5, A.2.6, A.2.9, A.3.2). Technique A.2.9-2.7 [Sufficient for (b)]: Providing conformance tests to show that the preview feature has the same UAAG 1.0 conformance rating as the target browser DEL. Technique A.2.9-2.8 [Advisory for (b)]: Documenting all of the accessibility features of the preview feature as compared to the emulated browser
Received on Wednesday, 31 May 2006 20:52:59 UTC