<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Brian,<br>
<br>
This is an interesting question. Today we have the ability via
AccessibleText to indicate both a caret location, and also a selection
(start, end). When you have a range of text selected, one end of the
selection has a caret and therefore keyboard manipulation of the
selection (shift-arrow) grows/shrinks the selection by manipulating
only one end of the selection range.<br>
<br>
In a multi-touch environment, there is (presently) no keyboard
mechanism for doing that at the same time on either end; you simply use
your finger. So... I'm not sure that we need a second caret until we
have a keyboard-operable way of doing that sort of manipulation.<br>
<br>
<br>
Regards,<br>
<br>
Peter Korn<br>
Accessibility Principal<br>
Oracle <br>
<br>
<blockquote
cite="mid:OF7423BACA.6CA90062-ON852576CE.007E4135-862576CE.007F1B1D@us.ibm.com"
type="cite"><font face="sans-serif" size="2">Hi all,</font>
<br>
<br>
<font face="sans-serif" size="2">At first glance, it seems obvious
that
an AccessibleText would only have one Caret. However I have
begun to question whether we will soon need an ability to represent at
least a second Caret. Multi-touch technologies are allowing
users to select with multiple fingers. For example, instead
of defining rectangles by a sequential first and a second corner
selection,
rectangles are defined by simultaneous corner indications of two
fingers.
The two finger motions of pinch and enlarge are becoming commonplace
in multi-touch interfaces. </font>
<br>
<br>
<font face="sans-serif" size="2">Thus I wonder how long it will be
before
there is a requirement of text selection from simultaneous touching of
multiple points, thus creating a need for two or more caret references
in a linear string of text.</font>
<br>
<br>
<font face="sans-serif" size="2">Please excuse me if this is an old
topic
that has been soundly considered.</font>
<br>
<br>
<font face="sans-serif" size="2">Regards,</font>
<br>
<br>
<font face="sans-serif" size="2">Brian</font>
<br>
<br>
<font face="Arial" size="2">Brian Cragun</font>
<br>
<font face="Arial" size="2">IBM AbilityLab Consultant<br>
Human Ability & Accessibility Center</font><font color="blue"
face="Arial" size="2"><u><br>
</u></font><a moz-do-not-send="true" href="http://www.ibm.com/able"><font
color="blue" face="Arial" size="2"><u>www.ibm.com/able</u></font></a><font
face="Arial" size="2">
& </font><a moz-do-not-send="true" href="http://w3.ibm.com/able"><font
color="blue" face="Arial" size="2"><u>w3.ibm.com/able</u></font></a>
<br>
<font face="Arial" size="2">W:(720)-663-2801 H:(507)288-2437</font>
<br>
<font face="Arial" size="2"><br>
</font>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Accessibility mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Accessibility@lists.linux-foundation.org">Accessibility@lists.linux-foundation.org</a>
<a class="moz-txt-link-freetext" href="https://lists.linux-foundation.org/mailman/listinfo/accessibility">https://lists.linux-foundation.org/mailman/listinfo/accessibility</a>
</pre>
</blockquote>
<br>
</body>
</html>