On 2/4/13 5:20 PM, Richard Schwerdtfeger wrote:
> Partially.
>
> So, cut, copy copy selected text to the clipboard. The details are
> handled by the rouser. Paste pasts to selected text or the insertion
> point (collapsed selection). What is the concern about clipboard
> functionality?
I'll have to dig through a month's worth of discussion on the list back
in June 2011. I'll try to get to that at some point during the week.
If you have time to look at it sooner look through the thread with
subject, "next changes to IAccessible2" here:
http://lists.linuxfoundation.org/pipermail/accessibility-ia2/2011-June/thread.html
>
> Rich
>
> Sent from my iPad
>
> On Feb 4, 2013, at 10:18 PM, "Pete Brunet" <[email protected]
> <mailto:[email protected]>> wrote:
>
>>
>> On 2/4/13 4:56 PM, Richard Schwerdtfeger wrote:
>>> Did you check with Nuance? What appends if replacetext is removed?
>> If you have a contact at Nuance please ask them to join the list.
>>
>> Only the clipboard methods are deprecated, which bascially means
>> don't use the cut/copy/paste methods until the IA2 spec can be
>> changed to support the varying implementations and ambiguities of
>> clipboard functionality. The rest of the methods are not deprecated,
>> i.e. deleteText, insertText, replaceText, and setAttributes. Does
>> that clarification help at all?
>>>
>>> Even if Nuance has not implemented it for say FF has someone
>>> approached them? We can' t just be supporting vision impairments.
>>>
>>> Sent from my iPad
>>>
>>> On Feb 4, 2013, at 9:35 PM, "Pete Brunet" <[email protected]
>>> <mailto:[email protected]>> wrote:
>>>
>>>> Hi Rich, At this point, since we couldn't find consensus and since
>>>> this release was supposed to done last Fall and since I was
>>>> informed that noone has implemented or shown a need for the three
>>>> clipboard operations, I'm inclined to not hold up the release any
>>>> further and handle this in a follow-on release if a project comes
>>>> along that needs clipboard functionality and provides resource to
>>>> drive the spec toward a well thought out definition of the
>>>> clipboard methods.
>>>>
>>>> Pete
>>>>
>>>> On 2/4/13 8:51 PM, Richard Schwerdtfeger wrote:
>>>>> Hi Pete,
>>>>>
>>>>> The reason for the editing functions was to allow a voice reco
>>>>> solution to select text, edit it, and perform clipboard operations
>>>>> for the mobility impaired. It is additional work to have a voice
>>>>> reco solution have to go through the additional work of doing the
>>>>> additional keyboard simulations for doing that function.
>>>>>
>>>>> So, these are single actions. AccessibleEditableText also allows
>>>>> you to replace text, and set attributes, which takes offsets and
>>>>> replacement text/attributes. Accessible actions are single action
>>>>> functions that don't take parameters. ReplaceText is not the same
>>>>> as pasting from the clipboard. It is really nice to have all the
>>>>> features in the same interface. Note: One could bind the single
>>>>> command functions (cut, copy, paste) to the same actions in
>>>>> accessible actions.
>>>>>
>>>>> The other problem you have with actions is where do you apply it.
>>>>> Do you know to apply it only to the document. If Editable text is
>>>>> applied to text content within the document then you should now
>>>>> where to find the interface.
>>>>>
>>>>> Rich
>>>>>
>>>>>
>>>>> Rich Schwerdtfeger
>>>>
>>
>> --
>> *Pete Brunet*
>>
>> a11ysoft - Accessibility Architecture and Development
>> (512) 467-4706 (work), (512) 689-4155 (cell)
>> Skype: pete.brunet
>> IM: ptbrunet (AOL, Google), [email protected] (MSN)
>> http://www.a11ysoft.com/about/
>> Ionosphere: WS4G
--
*Pete Brunet*
a11ysoft - Accessibility Architecture and Development
(512) 467-4706 (work), (512) 689-4155 (cell)
Skype: pete.brunet
IM: ptbrunet (AOL, Google), [email protected] (MSN)
http://www.a11ysoft.com/about/
Ionosphere: WS4G
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
