- From: David Bolter <david.bolter@gmail.com>
- Date: Wed, 22 Dec 2010 09:51:35 -0500
- To: Steve Faulkner <faulkner.steve@gmail.com>
- CC: HTMLWG WG <public-html@w3.org>, HTML Accessibility Task Force <public-html-a11y@w3.org>, Marco Zehe <marco.zehe@googlemail.com>, Richard Schwerdtfeger <schwer@us.ibm.com>, Cynthia Shelly <cyns@microsoft.com>
Right or wrong, exposing a role string (BSTR) for roles that don't have any fathomable MSAA role mapping is a FF tradition that AT now expects. As for exposure of the object, I don't expect we will change our heuristic of always exposing focusable elements (except I'm still mulling this over for aria-hidden subtrees). I find the Chrome behavior interesting... to move focus to the parent. Does this happen even when not launched in accessible mode? Cheers, David On 22/12/10 5:13 AM, Steve Faulkner wrote: > In firefox the input is still focusable and exposes a role of > presentation "Role: "presentation" [ BUG? State/Role should not be a > string ]"
Received on Wednesday, 22 December 2010 14:53:07 UTC