- From: <bugzilla@jessica.w3.org>
- Date: Sat, 18 Jan 2014 02:05:30 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23970
Jason Kiss <jason@accesscult.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason@accesscult.org
--- Comment #2 from Jason Kiss <jason@accesscult.org> ---
It will be good to get clarification from PF on the intended scope of usage for
menubar.
I'm not sure I agree that links don't represent "actions or functions" and that
therefore website navigation menus "aren't really menus".
I agree that the keyboard interaction pattern for ARIA menus is likely
unfamiliar to many users in the context of websites as opposed to desktop
applications, but presumably this is temporary, and can be mitigated in the
meantime by providing helpful prompts, either through some visual presentation
for sighted keyboard users, or help text for screen reader users.
That the links in the menu are set with role=menuitem and thus don't appear in
the screen reader's links list dialog is a potential concern. It would be good
to get some feedback from screen reader users as to how much of an issue this
is.
The Government of Canada's Web Experience Toolkit (WET) implements menubar for
its site navigation menu [1]. There's quite a bit of discussion around it on
their github repository [2]. From what I understand of the WET, they've done a
good amount of usability testing with a variety of users, including sighted
keyboard and screen reader users, and still appear committed to this
implementation.
[1] http://canada.ca/en/index.html
[2] https://github.com/wet-boew/wet-boew/issues/2680
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Saturday, 18 January 2014 02:05:32 UTC