Re: First draft of ARIA 1.1. "text" role

My 2 centsEach new role we introduce will create a learning curve for authors, many of whom will initially apply it incorrectly, killing the user experience, until an accessibility consultant tells them how to use it correctly. (Assuming the consultant is not also using it inappropriately - this is not to be taken for a given.) I say this based on a lot of personal experience.


If we do not need a new role we should not create it.




All the best

Lisa Seeman

Athena ICT Accessibility Projects 
LinkedIn, Twitter





---- On Wed, 12 Nov 2014 05:15:29 +0200 James Craig<jcraig@apple.com> wrote ---- 


> On Nov 11, 2014, at 5:41 PM, Cynthia Shelly <cyns@microsoft.com> wrote: 
> 
> I wonder if it might make more sense to change the definition of presentation or none to cover this scenario 
> 
> <p>I <img src="heart.gif" alt="love" role="none"> New York.</p> 
> 
> to read "I love New York" instead of "I New York" 
 
As Matt alluded, the ARIA 1.0 "presentation" role ("none" is a 1.1 synonym role of "presentation") does not expose any attribute or role semantics, so this would not expose the text alternative. 
 
> The glyph scenario is different, because it is text, and is often read as a single character. 
 
I don't think it'd always be limited to a single character. 
 
> But, do we need a role for that? Would this work instead? 
> 
> <p>I <span aria-label="love">♥</span> New York.</p> 
 
The role of the span is ambiguous here. Some platforms don't expose the span at all, preferring to flatten the selection string, so there is no element on which to hang the label. (Though that might just be an implementation detail.) 
 
James