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

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

From: James Teh <jamie@nvaccess.org>
Date: Wed, 24 Feb 2016 09:03:05 +1000
To: Joanmarie Diggs <jdiggs@igalia.com>, IA2 List <Accessibility-ia2@lists.linux-foundation.org>
Cc: ARIA Working Group <public-aria@w3.org>
Message-ID: <56CCE529.4080202@nvaccess.org>
Sounds great. I'm happy with this mapping.

Would this message be included in the concatenated description string 
for an object? I'm not sure if ATK has this, but in MSAA (and thus IA2), 
you can call the accDescription property and it provides the description 
as a string. Right now, that would include the text of anything listed 
in aria-describedby. I think it *should* include the error message myself.

Jamie

On 24/02/2016 5:42 AM, Joanmarie Diggs wrote:
> Hey all.
>
> We need to map aria-errormessage on the various platforms, including
> ATK/AT-SPI2 and IA2. Given the ongoing desire for cross-platform
> homogeneity, I'll toss out what I was thinking for my platform for
> consideration by IA2 folks.
>
> Proposal: Connect the message to the element with the error via the
> RELATION_DESCRIBED_BY/RELATION_DESCRIPTION_FOR relation pair and expose
> "errormessage" as an object attribute.
>
> Rationale:
>
> 1. An error message provides descriptive information about an object.
>
> 2. Exposure via a relation eliminates the need to tree dive to find
>     the error.
>
> 3. Accessible relations can have multiple targets, so this exposure
>     does not stomp on a non-error description while at the same time
>     eliminating the need for each platform to create a new relation
>     type(s).
>
> 4. The object attribute is needed to identify which target (if any)
>     is an error message.
>
> Thoughts?
> --joanie
> _______________________________________________
> Accessibility-ia2 mailing list
> Accessibility-ia2@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2

-- 
James Teh
Executive Director, NV Access Limited
Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess
SIP: jamie@nvaccess.org
Received on Tuesday, 23 February 2016 23:03:31 UTC

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