David, When a page author creates their own context menu is when you should have haspopup. The style gide says to use the same key strokes I believe. That essentially would steal the strokes from the browser.
I am referring to has popup in content and not the browser mapping. You
don't generate haspopup for the browser context menu now do you?
Rich Schwerdtfeger
CTO Accessibility Software Group
David Bolter
<david.bol...@gma
il.com> To
Sent by: accessibility-...@lists.linuxfounda
accessibility-ia2 tion.org
-boun...@lists.li cc
nuxfoundation.org
Subject
Re: [Accessibility-ia2] hascontext
04/05/2010 11:35 state
AM
Even though we could expose haspopup when we know there is a context menu
I'm not as sure we should since the way to invoke it is different. The user
would hear has popup, click (space bar) the widget and find no popup (since
it is a right click, menu key, shift-f10 that normally invokes the context
menu).
cheers,
David
On 05/04/10 11:57 AM, Richard Schwerdtfeger wrote:
I understand the use case ... A button may have a drop down menu and
a
context menu but would argue that having multiple pop-up menus of any
form
on an element is confusing. It would be better to simply have
haspopup. and
require the author to have one menu.
Rich
Rich Schwerdtfeger
CTO Accessibility Software Group
"Rob Gallo"
<rga...@freedomsc
ientific.com>
To
Sent by: <p...@a11ysoft.com>,
"'Alexander
accessibility-ia2 Surkov'"
-boun...@lists.li <surkov.alexan...@gmail.com>
nuxfoundation.org
cc
accessibility-...@lists.linuxfounda
tion.org, "'Hans Hillen'"
04/05/2010 08:26 <hhil...@paciellogroup.com>,
AM "'Marco Zehe'"
<mz...@mozilla.com>
Subject
Re: [Accessibility-ia2]
hascontext
state
I don't think there is a difference between a "context" menu and a
"pop-up"
menu. There are no roles distinguishing between these two types of
menus.
And even saying they are two types of menus is specious. Some menus
emanate
from the menu bar, and some do not. But after that, they're all the
same.
I am one user among many, but I don't feel a need for this.
Thanks,
RG
-----Original Message-----
From: accessibility-ia2-boun...@lists.linuxfoundation.org
[?mailto:accessibility-ia2-boun...@lists.linuxfoundation.org.] On
Behalf Of
Pete Brunet
Sent: Friday, April 02, 2010 2:18 PM
To: Alexander Surkov
Cc: accessibility-ia2@lists.linuxfoundation.org; Hans Hillen; Marco
Zehe
Subject: Re: [Accessibility-ia2] hascontext state
That seems like a good idea. What do others think? -Pete
Alexander Surkov wrote:
Hi.
It might be handy to have hascontext state to indicate the
accessible
has associated context menu. I realize it's very usual for
sighted
users to right mouse click everywhere checking for context
menu.
However it sounds it's not very comfortable for AT users to
press
shift+F10 on every element. This leads AT users might not know
there
is context menu. If we would have hascontext state then the
thing must
be much easier since AT could announce the context menu
presence like
it happens for popup menus. What do you think?
Thank you.
Alex.
_______________________________________________
Accessibility-ia2 mailing list
Accessibility-ia2@lists.linuxfoundation.org
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
_______________________________________________
Accessibility-ia2 mailing list
Accessibility-ia2@lists.linuxfoundation.org
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
_______________________________________________
Accessibility-ia2 mailing list
Accessibility-ia2@lists.linuxfoundation.org
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
_______________________________________________
Accessibility-ia2 mailing list
Accessibility-ia2@lists.linuxfoundation.org
https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
<<inline: graycol.gif>>
<<inline: pic14757.gif>>
<<inline: ecblank.gif>>
_______________________________________________ Accessibility-ia2 mailing list Accessibility-ia2@lists.linuxfoundation.org https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
