This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
This action item came out of the March 20 UAI TF meeting.
There are two ways. 1. Cache accessible tree before/on document load and cache relations. Watch mutation events of accessible tree and update cached relations. It sounds that's unique correct way but it might be hard to implement by AT client because of possible performance problems. 2. Calculate relations on request. Obviously AT client can't traverse whole document to calculate relations each time due to ongoing performance problems. AT client can do an assumption how relations are used in wild life and calculate correct relations in most cases. Mozilla assumes related elements are hosted in neighbourhood of the element relations are calculated for. So we go to the parent and check relations in its subtree, then we move to parent of parent and etc. Parents level is bounded by 5. It sounds this algorithm covers most of usecases. Any opinions?
*** Bug 6889 has been marked as a duplicate of this bug. ***
Obviously I mixed up "AT client" with "AT server" in bug description. Sorry for confusion.
Thanks for clarifying Alexander. All, I chatted with Alexander this evening and can speak about this bug at the next call.
Opera has this implemented. Would be good to ask them how they did it.
We don't this detail.