set target to OOo 2.0

.

as discussed with Malte Timmermann, Oliver Braun, Thomas Benisch -> target oOOLater

add keyword "accessibility"

re-targeted to OOo 3.0

As discussed with CN re-targeted to OOo 2.x.

this breaks also an automatic SDK-Test in
developersguide.basicanddialogs.toolkitcontrols

set target to OOo 2.4

As discussed with CN set to defect.

changed summary, as this issue is required from API testing

I had a look at Gnome and Java. In Gnome a spin button
appears as one element in the accessibilty hierarchy.
No special actions for incrementing or decrementing a value
are available. In Java a spin button also appears as one
element in the accessibility hierarchy, but the accessible
actions 'increment' and 'decrement' are available.

I discussed this issue with MT and OBR. As no AT tool
requests this functionality and the only customer of
such a functionality would be the API testing, we decided
to not fix this issue.

In addition, although this issue would be an enhancement of
the A11Y API, the accessibility keyword is wrong.
API testing needs the possibility to increment/decrement
the values of a spin button via UNO API. Due to the
shortcomings of the toolkit API the A11Y API is used
instead. But in principal one can think of extending the
toolkit API for providing this functionality.
Therefore I will remove the accessibility keyword and
set the target OOo Later.

changed summary

Created attachment 72536

The attached file by  misbirdcemu is spam. Please remove it.