aria-ISSUE-1007: aria-errormessage must require that the message be visible [ARIA 1.1] from Accessible Rich Internet Applications Working Group Issue Tracker on 2016-01-19 (public-aria@w3.org from January 2016)

From: Accessible Rich Internet Applications Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Tue, 19 Jan 2016 22:24:05 +0000
To: public-aria@w3.org
Message-Id: <E1aLeh3-0004FI-Dt@maia.w3.org>

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:24:07 UTC