- From: Joseph Scheuhammer <clown@alum.mit.edu>
- Date: Wed, 23 Sep 2015 12:44:43 -0400
- To: James Teh <jamie@nvaccess.org>, Alexander Surkov <surkov.alexander@gmail.com>, Richard Schwerdtfeger <schwer@us.ibm.com>
- Cc: W3C WAI-XTECH <wai-xtech@w3.org>
Hi James,
>
> The text frame role is currently a generic container. As such, we
> would try to traverse inside it for browse mode, rather than just
> accepting its accessible name. Would servers be exposing children in
> this case? I'm guessing not, in which case this should be fine.
If it matters, two use cases of role="text" entail that caret navigation
doesn't make sense. Here are examples from the spec [1], one that
involves a graphic and another using glyphs of stars.
Use with a graphic: <p>I <img src="heart.gif" alt="love" role="text">
New York.︎</p>
The image of a heart is given a role of text, and the text is "love".
Caret navigation doesn't apply to the graphic. Or, if it does, there is
only one caret position, not four ("love").
Use with glyphs: <p><span role="text" aria-label="3 of 5
stars">★★★☆☆︎</span></p>
Each glyph is rendered as either a filled-in or open star. And, in this
case, caret navigation of the string of glyphs/stars is possible. There
are five positions. But, the text string, "3 of 5 stars", has a
different length and different positions.
> Was ROLE_SYSTEM_STATICTEXT considered?
I was wondering about that too.
[1] http://w3c.github.io/aria/aria/aria.html#text
--
;;;;joseph.
'Array(16).join("wat" - 1) + " Batman!"'
- G. Bernhardt -
Received on Wednesday, 23 September 2015 16:45:12 UTC