Paul Novitski wrote:
Tell me if this would be a better scenario: When you select a menu
item, the page reloads with a set of breadcrumbs that spells out
the history of selected menu items, such as:
Thanks very much, Ian, your response to my posting was exactly the
kind of feedback I was l
Ian Anderson:
I think this would be immensely bad design for screen reader users.
This is a site map. What you may be missing is that too many links are
the bane of a screen reader user's life. They rely on using links as a
kind of binary tree to navigate the site - the last thing they benefi
Paul Novitski wrote:
Tell me if this would be a better scenario: When you select a menu
item, the page reloads with a set of breadcrumbs that spells out the
history of selected menu items, such as:
I think you are correct to be concerned about the issue, but this may
not be the optimal solut
At 11:26 PM 2/11/2006, Terrence Wood wrote:
the page reloads with a set of breadcrumbs that spells out the history
Essentially you are repeating information already available through
the browser history, and it still doesn't inform the user that there
is a new menu if that is your goal. Also, b
Paul Novitski wrote:
When the page reloads the screen-reader begins reading the menu from
the beginning again.
Correct.
The user would have to listen for a new sub-menu, but without really
knowing for sure whether a new sub-menu had appeared.
Correct.
browsing with a screen-reader must requ
I'd like to hear from folks who've used screen-readers:
What are the best ways to drill down into a nested list?
Consider a nested menu that's marked up as an unordered list
(UL). Select an item in the top-level menu and the page reloads with
a second-level menu of items opened up within the
