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

Hey again.

New proposal for the types:

ERROR_MESSAGE: Would go on the input which is invalid and point to the
element with the statement of what is wrong.

ERROR_SOURCE: Would go on the element which contains the statement of
what is wrong and point to the input which is invalid.

--joanie

On 04/11/2016 01:26 PM, Joanmarie Diggs wrote:
> Hey Jamie, all.
> 
> I don't believe we have a conclusion on this. So resuming the conversation.
> 
> If there's sufficient belief that errormessage is inherently different
> and that new API is called for, what about a new relation type?
> Personally, I am not jazzed by yet another relation type. But it is easy
> enough to add. We could add ERROR_FOR (or ERROR_MESSAGE_FOR) and ...
> what would the reciprocal relation be called?
> 
> --joanie
> 
> On 03/01/2016 06:33 PM, James Teh wrote:
> 
>> Everyone else is saying that errormessage is inherently different to
>> description. If that really is how it's meant to be according to the
>> ARIA spec (I disagree, but that's not relevant here), then mapping it to
>> description (even with an attribute) is a big hack. You can't have it
>> both ways; it's either just a specialisation of description or it's not.
>> Several people now say it's not the former, so it must be the latter.
>> And if it *is* the former, then it should be included as part of the
>> description text as well.
>>
>> FWIW, I don't like this whle thing at all, but it seems wrong to me that
>> the ARIA spec says it's not at all a description and the a11y specs say
>> it is. Personally, I think the ARIA spec *should* treat it as just an
>> extension of description, but I've already made that point and it
>> doesn't seem popular.
>>
>> Jamie
>>
> 
> _______________________________________________
> Accessibility-ia2 mailing list
> Accessibility-ia2@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
>

Received on Monday, 11 April 2016 18:23:42 UTC