W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2010

Re: Action 222 - http://www.w3.org/WAI/UA/tracker/actions/222

From: David Poehlman <poehlman1@comcast.net>
Date: Thu, 14 Jan 2010 10:05:54 -0500
Cc: UAWG list <w3c-wai-ua@w3.org>
Message-Id: <6569F5C7-B29F-4594-B8C4-52A45B7DD53D@comcast.net>
To: simon.harper@manchester.ac.uk
We need a search rap function.

On Jan 14, 2010, at 9:51 AM, Simon Harper wrote:

Hi there,

I was actioned to re update 4.6 (and have looked at this in combination with the implementation details. I've taken into account Greg's original comments as well as those expressed within the survey results. I've now come up with the following.

--------------

Guideline 4.6 Text Search

4.6.1 Find:
The user can perform a search within rendered content (e.g., not hidden with a style) for text and text alternatives, for any sequence of characters from the document character set. (Level A)

4.6.2 Find Direction: The user has the option of searching forward or backward from any selected or focused location in content. The user will be notified of changes in search direction; and when the search reaches the upper or lower extent of the content based on the search direction. (Level A)

4.6.3 Match Found: When there is a match, the user is alerted and the viewport moves so that the matched text content is at least partially within it. The user can search for the next instance of the text from the location of the match. Or, if the caret has been moved, from its new location. (Level A)

4.6.4 Alert on No Match: The user is notified when there is no match or after the last match in content (i.e., prior to starting the search over from the beginning of content). (Level A)

4.6.5 Advanced Find: The user agent provides an accessible advanced search facility, with a case sensitive and case-insensitive search option, and the ability for the user to perform a search within all content (including hidden content and captioning) for text and text alternatives, for any sequence of characters from the document character set. (Level AA)


IMPLEMENTATION DETAILS

*Intent of Success Criterion 4.6.1 Find:
To provide a function that allows the user to easily locate desired information in rendered or alternative text. Give the option of searching the alternative content. In the case of an embedded user agent, (e.g. media player), the embedded user agent provides the search for its content.
*Examples of Success Criterion 4.6.1:
A user wants to locate a text string in a long document. The user agent provides a mechanism for entering the desired text string, such as a text box with a search button.
A user wants to search for text in all views of the document, including views of the text source (source view)
A user wants to search the element content of form elements (where applicable) and any label text.
Related Resources for Success Criterion 4.6.1:
WCAG
4.6.2,3,4,5

*Intent of Success Criterion 4.6.2 Find Direction:
To enable the user to understand and control the direction of the search.
*Examples of Success Criterion 4.6.2:
The user wishes to find previously encountered text, before the current location of the caret.
The user has finished searching the text before the caret and has reached the upper limit of the page, they now wish to continue the search from the bottom of the document to the current location of the caret.
*Related Resources for Success Criterion 4.6.2:
WCAG
4.6.2,3,4,5


*Intent of Success Criterion 4.6.3 Match Found:
To enable the user to jump quickly to any found text, have the text spoken (say), and to continue searching from that point.
*Examples of Success Criterion 4.6.3:
The user wished to find text. This text was found, and the user investigated further to see if it was within the desired paragraph.
*Related Resources for Success Criterion 4.6.3:
WCAG
4.6.2,3,4,5


*Intent of Success Criterion 4.6.4 Alert on No Match:
Enable the user to understand when no text has been found and the search has come to an end.
*Examples of Success Criterion 4.6.4:
The user searched for text, but the desire text was not found and the search was terminated by the User Agent.
*Related Resources for Success Criterion 4.6.4:
WCAG
4.6.2,3,4,5


*Intent of Success Criterion 4.6.5 Advanced Find:
Enable the user to formulate a more advanced search, by which they can specify options such as, but not limited to, case sensitivity, and the ability to search within invisible textual components of the content such as video captions.
*Examples of Success Criterion 4.6.5:
The user wishes to find text which is currently hidden (via say, the CSS display attributes).
The user wishes to find text with a caption so that they easily locate that part of the video presentation.
The user wishes to search for textual descriptions hidden within embedded SVG.
*Related Resources for Success Criterion 4.6.5:
WCAG
4.6.2,3,4,5

--------------

Cheers
Si.

=======================

Simon Harper
University of Manchester (UK)

Human Centred Web Lab: http://hcw.cs.manchester.ac.uk

My Site: http://hcw.cs.manchester.ac.uk/people/harper/

My Diary (Web): http://hcw.cs.manchester.ac.uk/people/harper/phpicalendar/week.php
My Diary (Subscribe): http://hcw.cs.manchester.ac.uk/diaries/harper/SimonHarper.ics


-- 
Jonnie Appleseed
with his
Hands-On Technolog(eye)s
reducing technology's disabilities
one byte at a time
Received on Thursday, 14 January 2010 15:06:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 14 January 2010 15:06:31 GMT