Web page menu -- first or last?

#11

Jake <jake (AT) gododdin (DOT) demon.co.uk> wrote:

Quote:

In message <op.syuctzjq3jnr2w-wnt (AT) tbdata (DOT) com>, William Tasso
spamblocked (AT) tbdata (DOT) com> writes
...
Did you get sufficient replies elsewhere (I only subscribe to
alt.html.web-accessibility) to arrive at a conclusion?

You've seen all the replies ;-(

That's quite disappointing really - the names of the groups chosen looked
quite promising.

There's an ocasional poster (trevor) over in news:alt.www.webmaster that
has employed a blind webmistress - however he posts erratically (in both
senses <g>)

Quote:

I guess I'll stick to 'perceived wisdom' ... i.e. a 'skip to main
content' link at the start of every page (if necessary).

likewise
--
William Tasso

#12

On Tue, 18 Oct 2005 15:23:35 +0100, Jake <jake (AT) gododdin (DOT) demon.co.uk>
wrote:

Quote:

In message <op.syuctzjq3jnr2w-wnt (AT) tbdata (DOT) com>, William Tasso
spamblocked (AT) tbdata (DOT) com> writes
Jake <jake (AT) gododdin (DOT) demon.co.uk> wrote:

...
My interest is really in what people who need to use assistive
technology think, rather than what people who design the sites *think*
they need.

Thanks for posting, unfortunately replies from site builders are most
common. It would appear to a casual observer that those in need of
assistive technology are satisfied with the service they receive from
web sites in general.

Did you get sufficient replies elsewhere (I only subscribe to
alt.html.web-accessibility) to arrive at a conclusion?

You've seen all the replies ;-(

I guess I'll stick to 'perceived wisdom' ... i.e. a 'skip to main
content' link at the start of every page (if necessary).

Regards.

Out of interest, is the site specifically for users of assistive
technology, is it likely to get a higher than usual level of visitors
who do use assistive technology, or is it just a 'regular' site that
you are trying to make as accessible as possible?

Speaking from my own perspective (as somebody who is legally blind,
but who doesn't use assistive technology), it generally doesn't matter
what accessibility 'features' a web designer adds to a site, as my
browser is already set to display websites exactly as I need them
(just so long as they keep away from Flash and other things which
won't display in my chosen color scheme!).

However, from the limited exposure that I have had to screenreaders, I
would say that the 'perceived wisdom' appears correct. A skip to
content link, structured semantic markup, and some Access Keys
'should' cover most needs. Although more 'can' be done to aid those
who are using assistive technology, the need to balance accessibility
against standards compliance, browser compatibility and ease of use
for regular site visitors is a difficult one.

Regards

Janner

___

The VIP Consumer: consumer reviews and discussion from a visually impaired perspective.
www.vipconsumer.com

#13

Jake wrote:

Quote:

The conventional layout of a Web page has the menu appearing as the
first entry, with the main content following.

Perceived wisdom is that the first item on a page should, therefore, be
a 'skip to content' link so that frequent visitors can bypass the
repetitive menu system on each page, but can still quickly access the
menu when they want to by simply going to the beginning of the page
using, for example, the [Home] key.

One suggestion that is sometimes made is that the main content should be
placed first, followed by the menu. In this way there is no need for a
'skip' link at the beginning of the page -- although one thought is that
you now need a 'skip to navigation' link as the first page entry ;-)

If there is no link, then the user would presumably have to jump to the
end of the page and tab back through the links in the menu.

What would be your preference? Menu first -- or last -- on a page?

Or doesn't it really matter because that's not how you work anyway?
(e.g. use of 'list-of-links' for navigation)

And as a subsidiary question: how useful would it be to set up a jump to
menu or content via an Access Key?

Thanks
--
Jake (jake (AT) gododdin (DOT) demon.co.uk -- just a 'spam trap' mail address)

Hi Jake,

I'm a designer/developer at a university and have been doing some
extensive research over the past year. Although I'm not
visually-impaired myself, I've been working with a few people to try
and gather data regarding the use of assistive technology. Bob Easton
has been gathering some data regarding how screen readers actually
handle the markup of different accessibility practices and techniques.
(http://www.access-matters.com/)

Regarding content first versus menu first, it seems that most screen
readers read through the document in the order of the markup on the
page. This means if you would like your content to be read first, you
can put your menu after the content. Even if the menu appears top left
or top right through the use of CSS, most screen readers will read the
content first because it appears first in the markup.

If you organize the information into a few paragraphs with descriptive
titles (marked up as headers) for each section, most screen readers
will allow the screen reader user to view the list of headings on the
page and navigate to the one he or she is interested in. Users that
navigate in this way may not have use for the skip link if the menu is
before the content. However, users that allow the screen reader to
start reading from the top, can activate the skip link as it is being
read.

I used to believe that the skip menu link was for users specifically
using screen readers and would hide them off-screen using CSS (so
screen readers would read them) until a friend asked me why I was
hiding them. He commented that many people find them ugly and hide them
but, in fact, people with mobility problems are the ones that truly
benefit from them. My comment to him was, "Nothing that is truly useful
is ugly." and I stopped hiding them.

Other people that will benefit from the skip link are people that may
view your site on a smaller screen. I've been hearing a lot of feedback
from mobile users that appreciate a submenu of headings on a rather
lengthy page with "back to headings menu" links after each section
because scrolling is problematic on mobile devices.

Pam

#14

I sure wish when they design web pages they would set them up exactly just
like you described.

On Thu, 13 Oct 2005, Jake wrote:

Quote:

If I could take a few minutes of your time, I wonder if the sight-impaired
amongst you could comment on my thoughts regarding menu and main content
access on a Web page:

The conventional layout of a Web page has the menu appearing as the first
entry, with the main content following.

Perceived wisdom is that the first item on a page should, therefore, be a
'skip to content' link so that frequent visitors can bypass the repetitive
menu system on each page, but can still quickly access the menu when they
want to by simply going to the beginning of the page using, for example, the
[Home] key.

One suggestion that is sometimes made is that the main content should be
placed first, followed by the menu. In this way there is no need for a 'skip'
link at the beginning of the page -- although one thought is that you now
need a 'skip to navigation' link as the first page entry ;-)

If there is no link, then the user would presumably have to jump to the end
of the page and tab back through the links in the menu.

What would be your preference? Menu first -- or last -- on a page?

Or doesn't it really matter because that's not how you work anyway? (e.g. use
of 'list-of-links' for navigation)

And as a subsidiary question: how useful would it be to set up a jump to menu
or content via an Access Key?

Thanks
--
Jake (jake (AT) gododdin (DOT) demon.co.uk -- just a 'spam trap' mail address)