- From: Jan Richards <jan.richards@utoronto.ca>
- Date: Fri, 27 Jun 2003 12:07:45 -0400
- To: "List (WAI-AUWG)" <w3c-wai-au@w3.org>
New explanatory text for 1.5. Notes: - I added the word "rendered" to second success criteria since all tools allow unrendered equivalents to be searched - Do we also mean to imply searching non-text equivalents in external files (i.e. LONGDESC content? -- 1.5 Ensure the authoring interface allows the author to search within the editing views. [Priority 2] Rationale: Search functions facilitate author navigation of content as it is being authored by allowing the author to move focus quickly to arbitrary points in the content. Including the capability to search within text equivalents of rendered non-text content increases the accessibility of the search function. Success Criteria: The authoring tool MUST have a search function for every editing view. The author MUST be able to search for text within text equivalents of RENDERED non-text content. The author MUST be able to specify whether they wish to search content, markup, or both. -- Cheers, Jan -- Jan Richards, User Interface Design Specialist Adaptive Technology Resource Centre (ATRC), University of Toronto Email: jan.richards@utoronto.ca Web: http://ultrajuan.ic.utoronto.ca/jan/richards.html Phone: 416-946-7060 Fax: 416-971-2896
Received on Friday, 27 June 2003 12:07:40 UTC