RE: aria-ISSUE-1007: aria-errormessage must require that the message be visible [ARIA 1.1]

> We should also stipulate that the error message not be empty.

I find this bit confusing, does it cause a problem if empty?

E.G It is possible to render an empty element referenced via aria-describedby and to write content to it, which fires a description_change event, which is useful in cases where descriptions dynamically change based on user input.

So if aria-errormessage utilizes the same mappings, wouldn't this be possible here too?

I may be missing something.



-----Original Message-----
From: Accessible Rich Internet Applications Working Group Issue Tracker [mailto:sysbot+tracker@w3.org] 
Sent: Tuesday, January 19, 2016 2:24 PM
To: public-aria@w3.org
Subject: aria-ISSUE-1007: aria-errormessage must require that the message be visible [ARIA 1.1]

aria-ISSUE-1007: aria-errormessage must require that the message be visible [ARIA 1.1]

http://www.w3.org/WAI/ARIA/track/issues/1007


Raised by: Richard Schwerdtfeger
On product: ARIA 1.1

It is possible to map aria-errormessage such that it leverages the aria-describedby relationship by placing an object property on the target description. This would allow a separate mapping of a describedby relationship without a considerable change in the accessibility API. 

However, in order for the relationship to occur it must be visible as it would be hidden in the accessibility tree and not "stringified". 

In principle this should happen as the error message would need to be visible to everyone and often these error messages would be in live regions. 

We should also stipulate that the error message not be empty. 

This issue came up in the Core AAM mapping spec.

Received on Tuesday, 19 January 2016 22:53:37 UTC