W3C home > Mailing lists > Public > public-aria@w3.org > March 2016

Re: [Accessibility-ia2] Mapping of aria-errormessage for ATK/AT-SPI2 and IA2

From: Joanmarie Diggs <jdiggs@igalia.com>
Date: Tue, 1 Mar 2016 09:13:38 -0500
To: James Teh <jamie@nvaccess.org>
Cc: IA2 List <Accessibility-ia2@lists.linux-foundation.org>, ARIA Working Group <public-aria@w3.org>
Message-ID: <56D5A392.7000602@igalia.com>
Hey Jamie.

On 02/24/2016 06:14 PM, James Teh wrote:

> 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.

Really? Why can't we map it via described-by/description-for and then
use an object attribute to check if the descriptive element is an object

As for a new event, getting the same thing we get when an alert or
doorhanger is showing would be nice. I forget what event that is for you
-- just that whatever it is, I don't have it on my platform. For me it
would be object:state-changed:showing.

> If it's really such a new and separate
> thing, we don't have to worry about existing AT not getting the
> benefit.

Is that why you are proposing a new relationship?

Received on Tuesday, 1 March 2016 14:14:14 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:23:20 UTC