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

The same could apply to descriptions (e.g. a description could include a link to more info about how to fill in the field), but that's never been a factor before. Also, even if you believe this is more likely with errormessage for some reason, I'm guessing you still want AT to report the message when it appears and/or the control gets focus, in which case it can only be rendered as a string anyway.

Sent from a mobile device

> On 25 Feb 2016, at 9:33 AM, Richard Schwerdtfeger <richschwer@gmail.com> wrote:
> 
> Error messages may have additional content in there that needs greater semantic structure. For example, what if the error message had a link to a online help area about the topic. Converting it to a string would not work.
> 
> Rich
>> On Feb 23, 2016, at 5:20 PM, Joanmarie Diggs <jdiggs@igalia.com> wrote:
>> 
>> Hey Jamie.
>> 
>> Yeah, we have a description property which is a string. Right now, I
>> don't have a strong feeling either way about whether aria-errormessage's
>> text belongs as part of that value. So if you think it should be there
>> in addition to exposed via the relationship pair, I don't mind.
>> 
>> --joanie
>> 
>>> On 02/23/2016 06:03 PM, James Teh wrote:
>>> 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
>

Received on Thursday, 25 February 2016 01:05:39 UTC