https://bugs.freedesktop.org/show_bug.cgi?id=74284

--- Comment #16 from Marco Zehe <[email protected]> ---
(In reply to comment #15)
> Mozilla has some great API documentation here:
> 
> http://lxr.mozilla.org/seamonkey/source/accessible/accessible-docs.html
> 
> Ominously their drawing of what gets a peer seems to show them exporting a
> different tree to their internal representation - which (I guess) militates
> against exposing the layout peers: even though they may well provide useful
> semantic information to ATs.

Mozilla has only only one "real" window that gets exposed to assistive
technologies, meaning one that has a window handle, control ID and Window
Class. All the rest that is exposed is a hierarchy built from the XUL of the
Chrome, and the HTML of the web content, if any. So the parent/child
relationships are based on the DOM trees of both the browser chrome and
content. The accessibility hierarchy is a subset of the DOM hierarchy. In XUL,
vbox, hbox and other layout elements are left out, for example. They are for
layout purposes only, and the important thing for ATs to know is the location
and width and height of actual elements like labels, controls etc. How they got
there, and how many boxes are around them, is nothing assistive tecnologies
care about too much. :)

> I guess I didn't read what we're doing there yet; does the new VCL layout
> stuff have windows as real children of other windows ? or is the layout
> hierarchy tacked on the side ? ...

It looks very similar to what Mozilla is doing, exposing an accessibility
element hierarchy to assistive technologies that resembles the hierarchy of VCL
and document elements. And in here, these filler boxes that are used for layout
are exposed as whitespace. In Mozilla, the whitespace accessibles are
exclusively created for HTML:br elements to indicate to screen readers that
particular text doesn't run together.

Hope this helped!

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to