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

Re: role="text" and text frames

From: Rich Schwerdtfeger <richschwer@gmail.com>
Date: Wed, 3 Feb 2016 07:48:37 -0600
Cc: Cynthia Shelly <cyns@microsoft.com>, James Teh <jamie@nvaccess.org>, Alexander Surkov <surkov.alexander@gmail.com>, Joseph Scheuhammer <clown@alum.mit.edu>, Richard Schwerdtfeger <schwer@us.ibm.com>, "wai-xtech@w3.org" <wai-xtech@w3.org>, "public-aria@w3.org" <public-aria@w3.org>
Message-Id: <04C84748-3DAA-4CB8-A260-5757333BDB46@gmail.com>
To: "Schnabel, Stefan" <stefan.schnabel@sap.com>
This could be as all descendants are presentational with img

Sent from my iPhone

> On Feb 3, 2016, at 1:58 AM, Schnabel, Stefan <stefan.schnabel@sap.com> wrote:
> 
> I know that some screen readers have internal settings how to treat special characters, abbreviations and so on with regard to pronunciation, meaning etc..
>  
> What is missing here is an industry-wide concept/spec to handle aggregates of these things.
>  
> <span role="text" aria-label="3 of 5 stars">★★★☆☆︎</span></p>
>  
> is a clever example, but can’t this be resolved by simply declaring role=”img” + aria-label since this is pretty much an image?
>  
> With other words, isn’t for “ASCI ART” always role img appropriate?
>  
> And I wonder if for the other examples similar ARIA 1.0 means cannot be taken.
>  
> -          Stefan
>  
> From: Cynthia Shelly [mailto:cyns@microsoft.com] 
> Sent: Mittwoch, 3. Februar 2016 01:01
> To: James Teh <jamie@nvaccess.org>; Alexander Surkov <surkov.alexander@gmail.com>; Joseph Scheuhammer <clown@alum.mit.edu>
> Cc: Richard Schwerdtfeger <schwer@us.ibm.com>; wai-xtech@w3.org; public-aria@w3.org
> Subject: RE: role="text" and text frames
>  
> I think you’d get “f” moving by character, and caret navigation would move to the “f”. Basically, it becomes just some text in the text pattern, with nothing special about it. We could decide to put a format break there, or not.
>  
> I should be clear, though. I don’t especially like role=text.  I’m not convinced it’s needed, the issue in 1011 scares me, and there are many details like those you raise to work out.
>  
> From: James Teh [mailto:jamie@nvaccess.org] 
> Sent: Tuesday, February 2, 2016 2:40 PM
> To: Cynthia Shelly <cyns@microsoft.com>; Alexander Surkov <surkov.alexander@gmail.com>; Joseph Scheuhammer <clown@alum.mit.edu>
> Cc: Richard Schwerdtfeger <schwer@us.ibm.com>; wai-xtech@w3.org; public-aria@w3.org
> Subject: Re: role="text" and text frames
>  
> On 3/02/2016 7:53 AM, Cynthia Shelly wrote:
> 
> Once upon a <img alt=”foo”> time
> For role=text, the text pattern for the page would be “Once upon a foo time”
> What would happen if you move by character from the space after the "a"? Would you get "f" or "foo"? And what will pressing right arrow when using browser caret navigation (including contentEditable) do? These are the sort of questions that make techniques like this very problematic. The answers to these questions need to be well defined.
> 
> If UIA is really mapping this to the text pattern alone, it could be argued that IA2 should actually do the same; i.e. don't expose an accessible, just expose it in IAccessibleText. However, see the above potential gotchas.
> 
> Jamie
> 
> 
> -- 
> James Teh
> Executive Director, NV Access Limited
> Ph +61 7 3149 3306
> www.nvaccess.org
> Facebook: http://www.facebook.com/NVAccess
> Twitter: @NVAccess
> SIP: jamie@nvaccess.org

Received on Wednesday, 3 February 2016 13:49:11 UTC

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