Do we really need a dedicated relationship for this? Because the "target" of an AtkRelation is an array of objects, I would think we could use an existing relationship (e.g. described-by/description-for). Then we could examine the target object(s) to see if it's the one defined by aria-errormessage (exposed via object attribute).
--joanie On 08/11/2015 12:48 PM, Richard Schwerdtfeger wrote: > yes. We need it for ATK/ATSPI also. > > > Rich Schwerdtfeger > > Inactive hide details for Alexander Surkov ---08/11/2015 11:34:44 > AM---Hi. It looks like we need a new relation to expose aria-Alexander > Surkov ---08/11/2015 11:34:44 AM---Hi. It looks like we need a new > relation to expose aria-errormessage which refers to an element cont > > From: Alexander Surkov <[email protected]> > To: "[email protected]" > <[email protected]> > Date: 08/11/2015 11:34 AM > Subject: [Accessibility-ia2] aria-errormessage > Sent by: [email protected] > > ------------------------------------------------------------------------ > > > > Hi. It looks like we need a new relation to expose aria-errormessage > which refers to an element containing the error message. Should we have > a pair IA2_RELATION_ERROR_FOR/BY for that? > > THanks! > Alexander. > > [1] > _https://rawgit.com/w3c/aria/master/aria/aria.html#aria-errormessage________________________________________________ > Accessibility-ia2 mailing list > [email protected] > https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2 > > > > > _______________________________________________ > Accessibility-ia2 mailing list > [email protected] > https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2 > _______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
