- From: Cynthia Shelly <cyns@microsoft.com>
- Date: Mon, 8 Feb 2016 22:10:04 +0000
- To: Joseph Scheuhammer <clown@alum.mit.edu>, Alexander Surkov <surkov.alexander@gmail.com>
- CC: James Teh <jamie@nvaccess.org>, Richard Schwerdtfeger <schwer@us.ibm.com>, "wai-xtech@w3.org" <wai-xtech@w3.org>, "public-aria@w3.org" <public-aria@w3.org>
Yes, that's correct.
Again, I'm really not sure this is needed. I think leaving the image role alone would create as good a user experience in this case.
-----Original Message-----
From: Joseph Scheuhammer [mailto:clown@alum.mit.edu]
Sent: Friday, February 5, 2016 10:08 AM
To: Cynthia Shelly <cyns@microsoft.com>; Alexander Surkov <surkov.alexander@gmail.com>
Cc: James Teh <jamie@nvaccess.org>; Richard Schwerdtfeger <schwer@us.ibm.com>; wai-xtech@w3.org; public-aria@w3.org
Subject: Re: role="text" and text frames
Hi Cynthia,
Thanks for the detailed response; it helps me wrap my head around how UIA works in this case.
I have one question regarding case 4:
On 2016-02-04 4:42 PM, Cynthia Shelly wrote:
>
> 4)Once upon a <img alt=”foo” role=”text”> time
>
> Page text pattern is “Once upon a foo time”
>
> Accessible tree is
>
> Page
>
The accessible name computation is run on the <img> element to get "foo". But, in this case, you do not assign an accessible name property to any accessible, since there is no accessible for the <img> element.
Instead, the string "foo" is inserted into the page text pattern at the point where the img accessible would have been, had there been one.
Is that correct?
--
;;;;joseph.
'Die Wahrheit ist Irgendwo da Draußen. Wieder.'
- C. Carter -
Received on Monday, 8 February 2016 22:10:46 UTC