shouldn't this be a gtk+ bug then?

Could someone clarify for me what accessibility features we are unable
to offer as we cannot report the text and position of the text
associated with a slider.

I will use this to justify the GTK bug I will raise.

It is needed for the spacial screen-review. This accessibility feature
is intended to be a "screenshot" containg all the "text" information
on the screen, arranged on lines. In a line, elements should be
arraged too.
For example, a line that contains a button and a slider will look like
this (in case that slider will provide the displayed text)
[  OK  ]   |     50    |
[  OK  ]   |0          |
[  OK  ]   |        100|

In addition to the text and the extents of the text, do you need the
extents of each character of the text? This will impact what API
additions I propose for GTK.

I am confused by the diagram you have drawn in that I do not
understand where the 0 and 100 come from. I assyme that the 50 is the
text displayed for the value of a horizontal slider.

"In addition to the text and the extents of the text, do you need the
extents of each character of the text?"
That is correct. I need the same information as for any other text
that you provide.


"I am confused by the diagram you have drawn in that I do not
understand where the 0 and 100 come from. I assyme that the 50 is the
text displayed for the value of a horizontal slider."

What I meant in my drawing was : the displayed "text" (value) of the
slider it's displayed at a certain position, depending on the value.
In my drawings I assumed that the slider has values between 0 and 100,
so I draw 3 cases: if the value is 0 the value will be displayed in
the left part of the slider, if it is 50 than it will be displayed in
the midlle etc.

For a better understanding I will attach 3 screenshots and hor each
one I will write you the way that the line (containing the slider)
would look.

Created attachment 13983 [details]
[   Option 1    ] and a scale |0.00          | and an animation:

Created attachment 13984 [details]
[   Option 1    ] and a scale: |          100.0| and an animation:

Created attachment 13985 [details]
[   Option 1    ] and a scale: |     51.5   | and an animation:

Thanks for the clarification.

Fixing this bug must wait on bug 104811.

Created attachment 14792 [details] [review]
Propoesd implementation

The patch I have attached requires the patch attached to bug 104811.

Updating status_whiteboard field to reflect A11Y team's assessment 
of accessibility impact.

Apologies for spam... marking as GNOMEVER2.3 so it appears on the official GNOME
bug list :)

Patch committed to CVS HEAD.