WebAIM - Web Accessibility In Mind

E-mail List Archives

RE: Which should come first - navigation OR content?

for

From: ********
Date: Apr 25, 2006 10:50AM


Good question. When I read the article, I made the assumption that it was talking about such things as <title>Some name<title>, H1, H2, H3, form stuff like "label for" or field sets, that are in the code that speech users rely on to navigate the page quickly.

-----Original Message-----
>From: "John E. Brandt" < <EMAIL REMOVED> >
>Sent: Apr 25, 2006 10:16 AM
>To: 'WebAIM Discussion List' < <EMAIL REMOVED> >
>Subject: RE: [WebAIM] Which should come first - navigation OR content?
>
>
>Thank you for this reference. It's nice to see research as part of this
>discussion.
>
>[1] http://usability.com.au/resources/source-order.cfm
>
>That said, I am trying to understand what the authors means by "structural
>labels." They state:
>
>"All the participants indicated the inclusion of structural labels
>identifying the different levels of navigation on a web page was useful."
>
>In reading through the article, they comment that they have been using this
>(structural labels) for some time. I've not heard of this before so I am
>trying to understand what they are referring to.
>
>In looking at the code on the page of this article, I see they have added
>IDs (e.g. ID="footer") to all of the headings, unordered lists and for the
>header and footer elements. Interestingly, they did not include summary
>statements or IDs for the table elements.
>
>Is this what they are referring to as "structural labels? How are these
>rendered in the screen reader?
>
>Very curious.
>
>~j
>
>John E. Brandt
>Augusta, Maine USA
>www.jebswebs.com
>
>
>
>-----Original Message-----
>
>
>
>
>--
>Jens Meiert
>http://meiert.com/
>
>Webdesign mit CSS (O'Reilly, German)
>http://meiert.com/cssdesign/
>
> Address list
>messages to <EMAIL REMOVED>
>
>
>
>
>


________________________________________
PeoplePC Online
A better way to Internet
http://www.peoplepc.com