Hey all. Both ATK/AT-SPI2 and IA2 have "member of" and "node parent of" accessible relation types. I'm wondering if both are needed.
If memory serves me, "node parent of" was added as an after-the-fact inverse relation type for the "node child of" relation type. It's used in Gtk+ for trees and tables, and in ARIA implementations to map aria-owns. It seems to me that "node parent of" could also be used for whatever purpose "member of" was intended for. But I say that as someone who isn't seeing "member of" used on her platform. Given that some folks desire ATK/AT-SPI2 and IA2 be harmonized wherever possible, I figured I would ask if "member of" serves some helpful purpose in IA2 implementations. If so, I'm hoping your concrete examples will help me improve the ATK and AT-SPI2 docs. <smiles> If not, should we consider deprecating it on our respective platforms? Thanks in advance for your thoughts and insight on this matter! --joanie _______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
