On Thursday 2006-10-26 20:24 +1300, Robert O'Callahan wrote: > Aaron Leventhal wrote: > >Would there be a way to deal with this in script. For example, if a > >script wanted to get the accessible object for a given DOM node, the > >presshell would need to be part of the call to > >nsIAccessibilityService::GetAccessibleFor(). The presentation affects > >how accessibility is exposed -- we care about things like bounds and > >whether things are partially or fully offscreen. Each accessible must > >know what presShell it's in so that it can return that information. > > The DOM defines "views" which are basically presentations. This is what > you would want to use here. > http://www.w3.org/TR/DOM-Level-2-Views/
Although for at least some purposes I suspect that what end users using tools that use the accessibility APIs want is not details about a particular view of the document, but rather an additional view of the document. In other words, an aural rendering of a document should be its own view -- this allows it to be styled independently (via CSS), etc., although its focus could later be synchronized with another view (e.g., by keeping the input focus, plus a second concept of focus -- the material currently being read or currently visible, in sync between the two views). That said, I'm not familiar with the range of software that uses the accessibility APIs, or whether a single accessibility API can really give the best user experience for that range of software. -David -- L. David Baron <URL: http://dbaron.org/ > Technical Lead, Layout & CSS, Mozilla Corporation
pgpq49fZ0afKh.pgp
Description: PGP signature
_______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
