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

Re: AXTitleUIElement (was Re: Test Assertions with Tables)

From: Rich Schwerdtfeger <richschwer@gmail.com>
Date: Wed, 16 Mar 2016 14:22:36 -0500
Cc: Fred Esch <fesch@us.ibm.com>, SVG-A11y TF <public-svg-a11y@w3.org>, Accessible Rich Internet Applications Working Group <public-aria@w3.org>
Message-Id: <ACFFE2A0-D72C-42CA-B609-92B082FC9FBE@gmail.com>
To: Joanmarie Diggs <jdiggs@igalia.com>
Hi Joanie,

So, I am looking at this and AXTitleUIElement in http://rawgit.com/w3c/aria/master/accname-aam/accname-aam.html <http://rawgit.com/w3c/aria/master/accname-aam/accname-aam.html> an inadequate mapping for the following:

1. It only works if you have one ID. 
2. It maps differently if you have 2 IDs by stuffing a concatenated strip into AXDescription. 

Regarding, general label relationships, I donít value in exposing the relationship for labels in the API mappings unless you have a situation where the label has an embedded link that you MIGHT need to go to. 

So, I donít see value in mapping label relationships unlike descriptions where the content may need to be navigated. If people have not seed use cases in the wild where labels point to something else (embedded link) then we donít need the partial mapping for Mac and I donít see a critical need to follow a relationship on any platform for labels. 


Rich Schwerdtfeger

> On Mar 16, 2016, at 8:55 AM, Joanmarie Diggs <jdiggs@igalia.com> wrote:
> Hi Fred.
> On 03/16/2016 09:33 AM, Fred Esch wrote:
>> This is an ARIA question of what should be in the spec.
> I'm not sure that it is. I think it's an exit criteria question.
>> I am not a proponent of AXTitleUIElement, I am just coding to the spec.
> That's a good thing. :)
>> I don't have any problem changing the tests :) 
> I know. :) And what I am tossing out there is that **for the purpose of
> CR testing**, it might be worth doing so (slightly). In particular,
> testing for the computed string (like you do for ATK and IA2). The
> computed string for name and the computed string for description should
> be as per your expectations. If they are not, that means there is a bug
> in my implementation.
>> Or are proposing that SVG do something different and we have a different
>> name calculation than HTML?
> No. I am proposing that your group EITHER provide me with a real-world
> use case in which exposure via AXTitleUIElement **in addition to the
> existing computed string which is already in place as per your spec** is
> necessary, OR discuss if it is possible to do your CR testing based on
> the computed string.
> Hope this helps clarify things. And apologies for any confusion.
> --joanie

Received on Wednesday, 16 March 2016 19:23:06 UTC

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