On 08/11/2015 01:16 PM, Richard Schwerdtfeger wrote: > Sure, but then you need to separate out descriptions from error > messages, including text extraction for descriptions. We would have to > do this for descriptions and error messages.
At least in ATK/AT-SPI2, to get any relation, you have to get the relationset. So that call will be the same regardless of whether or not you create a new relation type. Having gotten the relationship, where things differ: * New relation type created: - Ask for the target object(s) - Get its/their text * Use existing relation type: - Ask for the target object(s) - Find the one(s) that are error-related via object attribute - Get its/their text So clearly a new relationship has the advantage of one less call and one less object attribute needed. (Good things.) But the price of those good things is that you need new API added (creation of the new relation types) so you cannot JustUse(tm) aria-errormessage. > Which evil do people prefer? Indeed. I don't have a strong feeling either way. But I'm leaning towards using the existing relationship because I don't see this feature becoming so widely used (in web apps, let alone in native apps) as to warrant the creation of new API in ATK and AT-SPI2 or make the use of an existing relationship a bad idea. So I'll leave it up to James. I think it's my turn to go with what he thinks is best. :) --joanie _______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
