Note, Jamie has been objecting against new relation for aria-errormessage [1].
[1] https://lists.linuxfoundation.org/pipermail/accessibility-ia2/2016-April/002046.html On Wed, Aug 10, 2016 at 8:33 AM, Alexander Surkov < [email protected]> wrote: > All reverse relations go at performance/memory cost, I would introduce > them iff AT needs them. I'm not sure I see a valid scenario, when they were > useful, thus deferring a decision to Joanie and Jamie, who knows more about > AT internal gear than me. > > On Tue, Aug 9, 2016 at 4:58 PM, Richard Schwerdtfeger <[email protected]> > wrote: > >> Those would be great. What would you have for reverse relationships? >> >> >> >> Rich Schwerdtfeger >> >> >> >> ----- Original message ----- >> From: Alexander Surkov <[email protected]> >> To: "[email protected]" < >> [email protected]>, James Teh < >> [email protected]>, Joanmarie Diggs <[email protected]>, Richard >> Schwerdtfeger/Austin/IBM@IBMUS >> Cc: >> Subject: aria-details and aria-errormessage mapping >> Date: Tue, Aug 9, 2016 2:12 PM >> >> Hi. >> >> ARIA 1.1 got two relation-like attributes: aria-details [1] and >> aria-errormessage [2], used to connect an element with content providing >> extra info. Rich mentioned that these attributes are likely need new >> IAccessible2 relations to expose them, which sounds reasonable. If that's >> the case, then we should end up with something like: >> >> An object containing details for the target object. >> IA2_RELATION_DETAILS >> An object containing an error message for the target object. >> IA2_RELATION_ERROR_MESSAGE >> Thanks. >> Alex. >> >> [1] https://www.w3.org/TR/wai-aria-1.1/#aria-details >> [2] https://www.w3.org/TR/wai-aria-1.1/#aria-errormessage >> >> >> >> >
_______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
