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

Re: role="text" and text frames

From: Alexander Surkov <surkov.alexander@gmail.com>
Date: Thu, 28 Jan 2016 08:06:15 -0500
Message-ID: <CA+epNsdt6=VPhV-jRyV0jR9sjah5wjTONVS1CLPj7m7r68v6uQ@mail.gmail.com>
To: Joseph Scheuhammer <clown@alum.mit.edu>
Cc: James Teh <jamie@nvaccess.org>, Richard Schwerdtfeger <schwer@us.ibm.com>, "wai-xtech@w3.org" <wai-xtech@w3.org>, public-aria@w3.org
Ok, I realize role="text" has its use case, and I'm good to support it. No
formal objections so far. Having said that, here's my thinking.

Everything that is a text should be accessible via text interface (like
IAccessibleText in IA2) and should be navigable by the user. role="text"
providing a text doesn't meet these criteria. If we could require the
browsers to support text interface for the role, but it seems we can do
nothing about the second part. It's just one extra step towards to
semantics disconnected from UI like aria-hidden true/false.

Then, if we do the statictext role which is a leaf, then I'm not clear how
we proceed with <p role="text">Oh, yeah, this is a whole paragraph</p>. We
may want to require the browsers to be smarter, stating that either 1) role
is ignored or 2) text container role is applied in cases where role="text"
is used on complex content.

Then, UIA mapping requires Text control pattern, which a text interface,
and that puts IA2 and ATK implementations out of line with UIA. While I do
understand these are different APIs, it won't make the implementators happy
who's going to supports all APIs.

Thanks.
Alex.

On Wed, Jan 27, 2016 at 4:58 PM, Joseph Scheuhammer <clown@alum.mit.edu>
wrote:

> Hi Alex,
>
> I believe everyone is okay with that.
>
> If anyone has an objection, please speak up.  If no one objects, I will
> change the mapping spec as appropriate by the end of the week.  That is,
> for role="text', the MSAA+IA2 role will be changed to
> ROLE_SYSTEM_STATICTEXT.
>
> http://rawgit.com/w3c/aria/master/core-aam/core-aam.html#role-map-text
>
> Thanks.
>
> On 2016-01-27 12:06 PM, Alexander Surkov wrote:
>
>> Hi, Joseph. As long as you all agree on static text, I'm good with that.
>>
>> On Mon, Jan 25, 2016 at 1:07 PM, Joseph Scheuhammer <clown@alum.mit.edu
>> <mailto:clown@alum.mit.edu>> wrote:
>>
>>     Hi Alex,
>>
>>     What's your take on this?
>>
>>     On 2016-01-21 5:24 PM, James Teh wrote:
>>
>>         On 22/01/2016 3:28 AM, Joseph Scheuhammer wrote:
>>
>>             On 2016-01-19 5:26 PM, James Teh wrote:
>>
>>                 I'm even more convinced that static text is the more
>>                 correct role recently, especially because ATK made the
>>                 same decision.
>>
>>
>>             Does that mean the correct MSAA+IA2 mapping of role="text"
>>             is ROLE_SYSTEM_STATICTEXT?  Or does it remain
>>             IA2_ROLE_TEXTFRAME, with the a display object attribute =
>>             "inline"?
>>
>>         It's controversial, but I think I'm now leaning towards
>>         ROLE_SYSTEM_STATICTEXT.
>>
>>         Jamie
>>
>>
>>
>>     --     ;;;;joseph.
>>
>>     'Die Wahrheit ist Irgendwo da Draußen. Wieder.'
>>                      - C. Carter -
>>
>>
> --
> ;;;;joseph.
>
> 'Die Wahrheit ist Irgendwo da Draußen. Wieder.'
>                  - C. Carter -
>
>
Received on Thursday, 28 January 2016 13:06:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:58:17 UTC