E-mail List Archives
Re: Using has-poppup to affect touch UIs
From: Alastair Campbell
Date: Dec 13, 2013 8:22AM
- Next message: Bryan Garaventa: "Re: Using has-poppup to affect touch UIs"
- Previous message: Steve Faulkner: "Re: Using has-poppup to affect touch UIs"
- Next message in Thread: Bryan Garaventa: "Re: Using has-poppup to affect touch UIs"
- Previous message in Thread: Steve Faulkner: "Re: Using has-poppup to affect touch UIs"
- View all messages in this Thread
Thanks Steve,
Expanding the meaning seems like a good idea if it doesn't impact other
things, I assume it's too late to rename it hasmenu?!
Given the name, it would not surprise me at all if other people don't
realise it was intended to apply to menus, anyone scanning the list trying
to achieve something will probably just pick haspopup. There's a similar
problem for dialog, where I see that used for content pop-overs (and then
NVDA won't read the content).
If it helps on the PF list, VoiceOver also announces "pop-up", but not
always menu:
role=link, haspopup: "Menu pop-up link [text name]"
role=button, haspopup: "pop-up button [text name]"
That's a bit odd, as I would have picked button for a menu pop-up, and link
for something that takes you elsewhere (including pop-over content boxes).
I guess there should also be a bug added for NVDA if it changes, as that
announces "menu" in all your cases.
Cheers,
-Alastair
- Next message: Bryan Garaventa: "Re: Using has-poppup to affect touch UIs"
- Previous message: Steve Faulkner: "Re: Using has-poppup to affect touch UIs"
- Next message in Thread: Bryan Garaventa: "Re: Using has-poppup to affect touch UIs"
- Previous message in Thread: Steve Faulkner: "Re: Using has-poppup to affect touch UIs"
- View all messages in this Thread