On 22/02/2012 6:54 PM, Alexander Surkov wrote:
The proposed document accessible concept is close to DOM document. ...
One example was get_accChild that can return child accessible
by uniqueID.
True, though the only time you ever need that is to test whether a given
node is within a document. If you are trying to do that, you probably
already have a reference to the document accessible.
All caret/selection methods are
fast on document accessible and slow on child accessible.
But in that case, we're probably dealing with an editable document,
which is a real ROLE_SYSTEM_DOCUMENT object. Trying to query for caret
or selection on an application or frame just doesn't make sense.
Theoretically anchorTarget is applicable to any document type,
requirement is the URL should contain '#' pointing to element.
Technically, that's true, but I don't see any use case for this in the
wild. Why would an AT want to query for anchor target on an application?
The problem is that all of this is abusing the idea of a document
property. In Gecko, an application might be the same internally as a
document, but that's not true from a user (and probably AT) perspective.
One option is to note that the document property just returns the
nearest document. If necessary, add a note stating that this will
usually be a ROLE_SYSTEM_DOCUMENT accessible, but that the definition of
document depends on the application. This makes a little trickier for
clients to know what they'll get, but it does allow for a bit of
flexibility.
Jamie
--
James Teh
Director, NV Access Limited
Email: [email protected]
Web site: http://www.nvaccess.org/
Phone: +61 7 5667 8372
_______________________________________________
Accessibility-ia2 mailing list
[email protected]
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
