- From: Matthew King <mattking@us.ibm.com>
- Date: Mon, 31 Jan 2011 15:39:38 -0800
- To: W3C WAI-XTECH <wai-xtech@w3.org>
>From the perspective of interpreting the ARIA spec, why would you think this is a bug? This is the behavior that Freedom Scientific interpreted as correct. As a child of window, it is not clear that a document mode is more appropriate than a application mode. I have been involved in conversation with Freedom Scientific on this topic, and they are open to further discussion. There are many considerations, and while I would like to see JAWS behave differently, I do understand how the current behavior can be interpreted as correct. Matt King IBM I/T Chief Accessibility Strategist IBM BT/CIO - Global Workforce and Web Process Enablement Phone: (503) 578-23329, Tie line: 731-7398 mattking@us.ibm.com James Craig <jcraig@apple.com> Sent by: wai-xtech-request@w3.org 01/31/2011 03:00 PM To James Nurthen <james.nurthen@oracle.com> cc W3C WAI-XTECH <wai-xtech@w3.org> Subject Re: Confusion about role of dialog I would agree that this is a JAWS bug. On Jan 31, 2011, at 7:26 AM, James Nurthen wrote: We have noticed that when using a role of dialog JAWS is going into application mode. Is this correct behaviour or a JAWS bug? I see nothing in the spec which states that this should happen. If this is NOT a JAWS bug, what role should we be using for a generic dialog container which may contain content (such as tables) as well as actions (buttons). -- Regards, James <oracle_sig_logo.gif> James Nurthen | Project Lead, Accessibility Phone: +1 6505066781 | Mobile: +1 4159871918 Oracle Corporate Architecture 500 Oracle Parkway | Redwood City, CA 94065 <green-for-email-sig_0.gif> Oracle is committed to developing practices and products that help protect the environment
Received on Tuesday, 1 February 2011 04:14:27 UTC