W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 2011

[Bug 13621] Allow user agents flexibility to meet user needs

From: <bugzilla@jessica.w3.org>
Date: Thu, 04 Aug 2011 06:55:34 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QorqA-0001gU-4C@jessica.w3.org>

Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> changed:

           What    |Removed                     |Added
                 CC|                            |bhawkeslewis@googlemail.com

--- Comment #2 from Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> 2011-08-04 06:55:33 UTC ---
(In reply to comment #0)

> Use case: Nadia is blind and using a web browser with a screen reader. The
> document contains a menu structure created with the HTML5 menu element, and it
> includes some very long menus with many groups of menu items separated by
> horizontal rules into various groups or sections. As Nadia uses the down arrow
> key to navigate through the menu items, she has to pause for each one to be
> read to her, so traversing a long menu takes a long time and a lot of effort.
> She would prefer to have the menu presented to her in hierarchical fashion that
> uses progressive disclosure, so she could navigate through the short list of
> sections, and then through the short list of commands in the desired section,
> rather than through one long list of items.
> Use case: Aidan is the opposite of Nadia. He uses an alternative input system
> and input is difficult for him, so he wants to reduce the number of actions he
> has to take. Therefore he prefers to see all the options visible at once so
> that he can choose one directly, rather than having to use mechanisms involving
> progressive disclosure. (He has even invested in a large, high-resolution
> monitor to support this work style.) Rather than choosing a sub-menu and then
> items from them, he'd rather have all the sub-menus and their items displayed
> together. Unfortunately, the HTML5 specification explicitly states that the
> menu element with a label must be presented as a sub-menu rather than displayed
> inline.

Could you please cite the text in the spec that prevents conforming user agents
meeting these use-cases? I think you may be confusing text describing what HTML
markup represents with text describing how what it represents must be presented
to the user.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 4 August 2011 06:55:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:59 UTC