I notice that AccessKit includes the concept of a node owning another node, but this doesn't seem to be implemented anywhere?
I'm interested in what the design for this is envisaged to be? If I set Node A to own Node C, but Node B marks it C as a child, will AccessKit handle this "properly"?
I would assume accesskit could gracefully handle this such that ATs see Node C as a child of A NOT B? Is this desirable?