ISSUE-1013: Is there a need for an aapi event for aria-errormessage

Isn't the presence—or absence—of aria-errormessage enough?

The question is: how does the AT know when the error message text is relevant?

The spec currently says that aria-errormessage is used in conjunction with aria-invalid; hence, the signal that the error message is pertinent is when aria-invalid is set to true. Setting aria-invalid to true will cause an AAPI event for everyone but UIA [1]. That may be sufficient, although something needs to be done in the case of UIA.

Also, the error message will be shown when it's relevant. That will also cause events in the AAPI [2]. That may also be sufficient.

Then again, it might be very useful to have a specific "error-message-asserted" event that targets error messages only. Dunno.

[1] http://rawgit.com/w3c/aria/master/core-aam/core-aam.html#event-aria-invalid
[2] http://rawgit.com/w3c/aria/master/core-aam/core-aam.html#mapping_events_visibility

Latest from James Teh:
"If you really do want errormessage to be treated as an entirely separate thing, then I have to change my position on this: we need a new relation and new events. If it's really such a new and separate thing, we don't have to worry about existing AT not getting the benefit." [1]

[1] https://lists.w3.org/Archives/Public/public-aria/2016Feb/0419.html

WONTFIX

There are already numerous events, tied to live regions, that are adequate (some would say are actually spam).

Joseph withdraws the issue, also.

Closing.