Hi, Rich.
The IA2_ROLE _TEXT_FRAME role is used in Firefox for text containers, for
example, for acronym, abbr, html:q, for span elements with ARIA markup. Also
it's used for HTML in...@type=file.
Thanks.
Alex.
On Wed, Apr 14, 2010 at 9:01 AM, Richard Schwerdtfeger sch...@us.ibm.comwrote:
Hi Alex,
Do these controls actually look any different from a normal input
type=text? In my opinion, if the control doesn't look different
visually, there's probably no need for an AT to report it differently
either. I guess there's no harm in exposing it as an object attribute in
case an AT
Hi, James.
AFAIK UI of new controls is under discussion. I expect they might have
different styling, additional images, or more complex UI like in the
case of searchbox, it might have search and clear buttons. Also I
assume UI might be browser-dependent. But originally I was interested
if screen
Hi Jamie, all,
Could you imagine this input type information helping prediction based
alternative input technology such as speech input?
cheers,
David
On 14/04/10 6:58 AM, James Teh wrote:
Hi Alex,
Do these controls actually look any different from a normalinput
type=text? In my opinion, if
I like the idea of exposing the information as an object attribute. I think
a case could be made that users might find the information useful or
interesting.
Also, what is the purpose of such fields from the sighted/page author's
point of view? Is it merely to provide better data formatting?
Jamie,
I want to throw in that these form elements will have associated labels
(part of the markup) and an autocomplete feature which is quite different
than we would normally expect.
Rich Schwerdtfeger
CTO Accessibility Software Group
